151–160 of 198 posts
Claude is already pretty handy with Typescript, but with all of the built in libs in Bun I wonder if there is even more to squeeze out.
Earlier quoted context omitted.
Some people still make crafts by hand.
Plenty of people on that list maintain serious production systems or open source projects in use by a wide variety of people. It's not just some nerds tinkering in their basement.
Coding agents have really only taken off in the last 10 months. So it is still early.
Earlier quoted context omitted.
1.4 also adds a lot of features so its more than a port. Plus Claude Code has been using the rust port since atleast July 19. So its definitely less than 3 months.
Or, more likely, the amount of crappy auto generated code and “features” they crammed into this release resulted in so many bugs that a “simple rewrite” would up being 3 months of whack-a-mole with the issues they created. That’s the predictable result from the lack of engineering discipline involved here.
This is a huge win for Bun & Anthropic. I've been keeping an eye on Bun development cycle since they announced the Rust rewrite and the huge drama and backlash it generated. They seem to be proving the skeptics wrong with this release.
This was an incredible demo for Claude. The runtime hosted Claude Code for months and I never saw the slightest issue. Wholly machine ported. Truly amazing.
We're never going to know how much it cost and how many hours of engineering time it took behind the scenes.
apparently there's some kind of automated differential fuzzer to discover Node.js incompatibilities, but probably that's behind the curtain.
We might never know the exact dollars and cents amount, but we can make pretty well calibrated guesses.
Earlier quoted context omitted.
Yes, I'm fine with the AI rewrite, just don't claim it was done in 11 days when it actually took ~50.
The rewrite part of get to functionally equivalent to the existing zig version in rust did in fact take 11 days based on the available data. When that was done, they spend some time on a ton of new features and hardening and bugfixing that the Rust rewrite enabled. This took additional time.
I guess this is much reduced by now, and the effort required on that front should not be rejected from being part of the migration.
omfg, that's a long post. How is this even possible? I know we're all using AI, but Bun seems like the one singular project where there's just been a crazy increase in the amount of output, a 10x on the 10x. How are they doing this?
Unlimited full-access to one of the best LLMs / agents on the market, and 80 hour work weeks probably.
Earlier quoted context omitted.
Plenty of people on that list maintain serious production systems or open source projects in use by a wide variety of people. It's not just some nerds tinkering in their basement.
I don't doubt this is the case. Even if they're producing code by hand, surely they have LLM helpers by now. Coding agents have really only taken off in the last 10 months. So it is still early.
We are billions of people opposed to AI as an ecocidal tech and a heteronomous political project, including much of the IT sector. Just because you only follow grifters and scammers trying to profit from the AI bubble doesn't mean "surely" we all follow those trends.
I recently pivoted to Rust for the backend development, after getting tired of the nodejs ecosystem fragmentation and how fragile things feel. Bun seems very interesting since it allows you to do so many things without pulling in 3rd party libraries and bundlers? Is anybody using it instead of nodejs? how's the experience so far? I might have to give it a try. Yes, I know there's probably better options than Rust for…
The most appealing thing of Go to me is the good batteries including tooling. I don't use it much outside of little personal projects where I really don't want to deal with dependencies and want a small binary.
Backend + web API + the actual web pages all contained in a single file. If you have sane defaults, deploying is literally just copying a single executable over.