7 comments

  • hootz 17 minutes ago
    Oh well, I really like using Bun and I get kinda sad about the turn they are taking after the Anthropic acquisition. I really want a good Node with batteries included, but I don't want it vibe coded.
    • umvi 5 minutes ago
      Honestly I hope agentic AI ushers in a new age of minimal-SBOM software. I myself am moving all of my projects towards nearly 100% vanilla where possible. For example, golang. Why use [insert web framework] when you can just use vanilla for 99% of web apps?

      There's something really satisfying about a go binary with minimal dependencies running in a busybox docker container.

      • echelon 2 minutes ago
        Frameworks and ORMs were the pre-agentic AI "iron man suit".

        I'm quite liking how good Claude Code Opus is at Rust + sqlx (raw SQL with type safety) + actix-web.

      • maxloh 5 minutes ago
        I understand their decision. How could the maintainers understand their codebase if most of it was not directly written by them? It is impossible to review the entire rewritten codebase. There are just too many lines of code.
        • trollbridge 1 minute ago
          Right. I now have responsibility for rather large codebases where the person who generated it with agentic tools (I'd say it's better than pure 'vibe coding') barely understands how it works. This is okay for unimportant parts of the codebase, but completely unacceptable for a critical piece of infrastructure where it really needs to be well thought out.
        • satvikpendem 7 minutes ago
          As long as Deno support is still there I'm not sure why you need anything else. It's not vibe coded slop for one.
          • mvdtnz 9 minutes ago
            Wow, bun support was just added in November last year (I think). That's a lot of work to throw away, but you can't argue with their reasoning.
            • antonvs 16 minutes ago
              Reason #2 is purely speculative. It’s disappointing to see technical decisions being made on such grounds.
              • smlavine 11 minutes ago
                All dependency management is speculative. You've got to hedge your bets that the dependency is reliable and fit for purpose. It is reasonable to view Bun's recent choices as increasing the risk associated with depending on it.
                • malfist 12 minutes ago
                  What part of the recent history of vibe coded projects has not resulted in low quality, bug laden code? Dismissing this a "purely speculative" is just like dismissing the weather report as "purely speculative" when deciding what to wear in the morning.
                  • cortesoft 1 minute ago
                    There is quite the selection bias going on here... you aren't hearing about the successful projects.
                  • happytoexplain 6 minutes ago
                    It's a common fallacy among tech folks to believe that every decision can be made from 100% deterministic grounds ("X decision will result in Y percent change"). In reality, successful decision-making often involves speculation. The speculation in question is within the bounds of reason. You may disagree, but the fact that it is speculative isn't the problem.
                    • mvdtnz 10 minutes ago
                      It's a reasonable decision to not take a dependency which doesn't meet your own engineering standards. People in the JS community could learn something from that.
                    • fastball 11 minutes ago
                      The "to vibe code or not to vibe code" holy war is now in full swing.