every couple years someone rewrites the whole toolchain and we collectively agree the last one was the mistake. good to know the cycle still works.
The cycle's will never gonna end. It's just gonna be incredibly faster now.
Bun 1.4
191–198 of 198 posts
Re: Bun 1.4
#192Earlier quoted context omitted.
I fully AI-driven rewrite of a massive codebase from one language to another within a reasonable release-cycle has never been done before. There was a lot of sentiment around the lines of: - Bun is done for, it's all slop now - there's no way a fully AI-written codebase can work - Jarred is an idiot for trusting AI to rewrite the whole thing - they're never going to release this, there's going to be a billion of bugs…
I don't think this release definively proved all of this wrong, no.
That's true, it was when they stealthed released it in a application that millions use and no one noticed.
Re: Bun 1.4
#193Earlier quoted context omitted.
> Why would I want everything reimplemented in this massive binary? Why would Bun be anymore in touch with nuances of all these different technologies then individual projects dedicated to their own speciality? It's funny because the top article on HN is about a malicious rust crate package, and people keep making comparisons to js/npm and how both language suffer from frequent security issues because they have weak…
I saw a post recently about how LLMs are much more effective in Ruby on Rails because it's batteries included, so you don't get so many implementation details crapping up the context window. I assume the same benefit applies to humans as well!
Those are strong claims and I think we need better evidence to support it. Most of the backend frameworks are batteries included to extent like Django, Laravel, Phoenix. Also many decisions made by Rails team are quite debatable, hotwire and getting rid of TypeScript being top ones recently.
Tbh we need to do some real research about it, because all those articles are just feelings that it seems to work better. But mostly it feels better, because we got stronger models and improved agent harnesses
Re: Bun 1.4
#194Earlier quoted context omitted.
I saw a post recently about how LLMs are much more effective in Ruby on Rails because it's batteries included, so you don't get so many implementation details crapping up the context window. I assume the same benefit applies to humans as well!
If agents are good at RoR, it's ironic because they're bad at Ruby. They aren't good at holding a model of the 20 different things various code you've loaded has monkey patched, no longer respecting their original contracts.
I don’t believe they are better at Ruby. Agents got better overall and people draw bad conclusions from their anecdotal evidence. Ruby on Rails is mostly DHH cult with people praising Ruby as poetry.
This is coming from someone working 13 years as Ruby dev. I love the language, but I want to be honest that I didn’t had experience with other languages before and seeing statically typed languages (Java, TypeScript), Elixir opened my mind to the amount of cargo cult inside Ruby community stemming mostly from people limited to knowing only 1 language.
Re: Bun 1.4
#195Earlier quoted context omitted.
I fully AI-driven rewrite of a massive codebase from one language to another within a reasonable release-cycle has never been done before. There was a lot of sentiment around the lines of: - Bun is done for, it's all slop now - there's no way a fully AI-written codebase can work - Jarred is an idiot for trusting AI to rewrite the whole thing - they're never going to release this, there's going to be a billion of bugs…
I don't think this release definively proved all of this wrong, no.
Which one did it not prove wrong? The fully AI written version of Bun has released, fixed a ton of bugs that existed in the zig version, added a lot of new features and performance improvements and has been shipping with every single installation of claude code for months, the most widely used LLM-harness out there.
By every single measurable metric this is better software than the old hand-written version ever was.
Re: Bun 1.4
#196It's weird their promotional video repeats "you can do without installing dependencies", if I want headless browser testing is that wrong to install a project that offers that? Why would I want everything reimplemented in this massive binary? Why would Bun be anymore in touch with nuances of all these different technologies then individual projects dedicated to their own speciality? JS Runtime, Package Manager, Test…
Its strange how flip floppy the JS ecosystem is, because go back literally 1-3 years or so and the BIGGEST complaint was the lack of a standard library and having to use a package for everything. But now that Bun is actually doing it its somehow bad? Its also still open source, so those implementations you mention need dedicated teams can still get the attention they need by the community if needed. I'm on the side t…
I would argue it is more of a politcal problem, rather than in tech problem.
It is the same idea arounds LLM: people loving it keep praising it and criticise the haters, people hating it keep nitpicking it and criticise the lovers, and both of them tries to poach you to go to their side.
So no matter what, those people would also try to find things to shit on Bun if they make a move even if it is considered rational.
So the whole thing is never about tech anymore, it is about wanting Bun to succumb to their will.
Re: Bun 1.4
#197If Bun weren't owned by Anthropic, wouldn't they now be a little screwed?
Presumably no one at Bun will know their codebase as well as they used to (unless there was a lot more human review than they claim), and so they're tied to AI, no matter how much tokens cost in future.
It feels anyone else doing this would also now be owned by Anthropic, just without the payment.
Re: Bun 1.4
#198Earlier quoted context omitted.
You're celebrating Bun 1.4 on literally day one. I'd suggest waiting for it to hit prod. irrespective of the political turmoil etc Quite the hand-wave!
claude code uses bun written rust. and it has been in prod for a month or so. I am finding it hard not to celebrate because it was quite literally a +1M -4K line change that is touching people today. > irrespective of the political turmoil. I was mostly concerned with the technical perspective of firing 80% of people by stack ranking. the consensus in HN at the time was that twitter had months left before all product…
X is dead, that's not just fine.