Live data from Hacker News

Bun support is now limited and deprecated

github.com

511–520 of 646 posts

Re: Bun support is now limited and deprecated

#511
post #132

What does this use bun for? I thought this was a python project?

They need a JavaScript runtime to execute some challenges that certain pages present (like YouTube)

They used to have their own "youtube script interpreter" that was kind of fascinating. But yeah as you said they switched to proper js runtimes recently.

Re: Bun support is now limited and deprecated

#512
post #234
post #223

Earlier quoted context omitted.

Every single macOS update the top comments are about giving it six months to stabilize, but when a program’s biggest ever rewrite involves a lot of AI, the top comment is calling you irrational if you don’t YOLO it, and probably a jerk, too.

YOLO? Bun has an extensive test suite and this implementation passed the test suite. Can we at least try to be a bit more accurate and less hyperbolic? I will continue to use Bun because the same people that made bun have made this decision. I trusted them one week ago. I have used bun for the past 2 years, and so have many others. I'm not about to just assume they've become immature idiots yolo'ing stuff overnight.…

They can have 100% coverage for all I care, you don’t push 1 mil loc change and call it a day.

> I'm not about to just assume they've become immature idiots yolo'ing stuff overnight. They're still the same people they were a week ago. Or two weeks ago.

They’ve literally sold out to Anthropic.

Re: Bun support is now limited and deprecated

#513
post #269

Earlier quoted context omitted.

>> same people that made bun have made this decision Are they the same people though? Their interests, goals, environment, incentives, boss etc etc all changed after they got acquired by Anthropic. Its not uncommon for a big company to acquire a smaller one and completely destroy that product to serve the parent company's goal.

You can go read all the details on Jarred's X account - including the progress, how it was thought out, strategy, that they're aware that it looks like zig still, etc etc etc. Speaking of environment though, everyone neglects to mention that the Bun core team now has access to Claude Mythos. You think they haven't already run Mythos against this? So they have private access to the best cybersecurity scanner known to…

> You can go read all the details on Jarred's X account - including the progress, how it was thought out, strategy, that they're aware that it looks like zig still, etc etc etc.

https://news.ycombinator.com/item?id=48019226

> This whole thread is an overreaction. 302 comments about code that does not work. We haven’t committed to rewriting. There’s a very high chance all this code gets thrown out completely.

I ain’t reading a single thing from the guy after this one.

Re: Bun support is now limited and deprecated

#514
post #101

Earlier quoted context omitted.

FYI in case you aren't aware, the rewrite was shipped, and then had to be reverted due to issues being discovered. That's "Jarred's high quality bar" you're so confident in.

The whole point of having canary builds is that they're unstable. That's why they're called canary. Rockets failing in test flights isn't a bad thing.

Runtime that you build on isn’t a rocket. It’s like seeing a bridge collapse in front of your eyes.

Re: Bun support is now limited and deprecated

#515

Earlier quoted context omitted.

He plays around with a toy project in a separate branch, tells everybody to relax that's just an experiment that has no chance of being merged, then abruptly merges 1m lines of code not seen by a human, effectively zeroing out all the contributions ever made by anyone to bun, including contributions in progress. At the same time, his arguments in favor of Rust are sound, there is no doubt about that.

>that's just an experiment that has no chance of being merged Yeah he never said that.

> This whole thread is an overreaction. 302 comments about code that does not work. We haven’t committed to rewriting. There’s a very high chance all this code gets thrown out completely.

https://news.ycombinator.com/item?id=48019226

Re: Bun support is now limited and deprecated

#516
post #84
post #12

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, 1 million lines to be exact [1]. [1]: https://github.com/oven-sh/bun/pull/30412

So it was possible to write ~2 million lines of (mostly) zig, but it's not possible to review ~1 million lines of rust, even though the same test suite included in those 2 million lines of zig can still be used? I'm not convinced the rewrite is a good idea and will work out, but I'm equally unconvinced by your argument.

In a week?

Re: Bun support is now limited and deprecated

#518

Earlier quoted context omitted.

How many lines of translated code would have been acceptable? What about before AI all the machine translated projects that people used for years without a single complaint? The person who did this was the lead for Bun from the get go no? So it stands to reason that they are one of the highest authorities in Bun itself.

What is the essence of a program? The name? No. The author? No. The test suite? No, testing is hard and most projects don't do enough of it. The code? Not really, code can be rewritten. The history of the program being executed by its users? Ding ding ding. Yes, it's this one. Bun no longer exists. What exists now is a program that has the potential to be Bun but at this time is not Bun because it has no history of b…

i highly disagree with that framing. the essence of a program is not the fact that people have been running it

you could write a great program and never run it. does that mean the program does now not exist? or that it is not a new, unique thing?

if anything, the essence of a program is made up by all of the things you mentioned!

Re: Bun support is now limited and deprecated

#519
post #154
post #73

This decision seems to based more in politics than engineering. Have you observed Bun have more segfaults, OOMs, etc, since the Rust rewrite? Have you noticed more security vulnerabilities? Have you seen more bugs? (Of course you haven't, the rewrite hasn't even landed yet.) It seems that you are making this decision because you get a bad feeling when thinking about AI involvement. I don't select my engineering tools…

> This decision seems to based more in politics than engineering. You are 100% right. This is a decision made on VIBES and not evidence. The proof is here: > Bun was recently rewritten in Rust using Claude, and its development seems to have taken a turn towards being fully vibe-coded. This is alarming and disappointing for a number of reasons, and frankly it seems like a future headache that we'd prefer to avoid. The…

> They haven't tested it, they haven't found a single problem. They just don't like AI code and they're clearly saying "the fact that the project tested every line of code and it passes all tests doesn't matter to us. The fact that it's vide coded by people who literally make coding LLMs also doesn't matter." Pure ego, no data.

So an OSS project now owes testing to hyperscalers? Lol!

Re: Bun support is now limited and deprecated

#520

I see Bun’s Rust rewrite (esp the style how it was done) as a form of massive internet trolling for PR reasons. By making a bigger fuss about it, we’re feeding the troll

They are. Just wait until Jarred releases his blogpost and Anthropic marketing machine kicks in.
Post reply on HN