Live data from Hacker News

Bun support is now limited and deprecated

github.com

491–500 of 646 posts

Re: Bun support is now limited and deprecated

#491
post #38

Earlier quoted context omitted.

I think it's hilarious how hopeful people were at the acquisition that Bun would be able to continue on mostly as it had been but then that all got completely thrown away and trashed. (Hilarious in the way that's terribly sad, of course.)

How has it been trashed? Does the Bun software not work anymore?

Spatting on community was a big deal in OSS circles.

Re: Bun support is now limited and deprecated

#492
post #49

Earlier quoted context omitted.

They literally threw out every line of code that existed before and rewrote it in a completely different language, seemingly on a whim. That's how it was trashed, in the very literal sense that all of the existing project was tossed in the trash in favor of a completely brand new code base. That's a big deal even if you ignore the coding agent aspects.

But it's not a big deal, code is cheap. This is hand-wringing about nothing.

> But it's not a big deal, code is cheap.

So just maintain Bun fork of yt-dop, problem solved.

Re: Bun support is now limited and deprecated

#493
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

I'm very skeptic that they read the entire codebase of Bun prior.

> I'm very skeptic that they read the entire codebase of Bun prior.

Well, they didn't really need to. A complete rewrite is effectively a different project. You may feel comfortable using a new project in prod, but most people are not.

Project A: used in production for 3 years - high trust.

Project B: Has yet to be used in production - low trust.

IDGAF about automated tests, let other users shake out the inevitable bugs that show up in prod and after a few years of stability, then we'll see.

To me, it's not about whether humans reviewed the code or not (they didn't), it's more about "here's this brand-new shiny codebase of ~1m Sloc, of which exactly zero lines has been used in prod".

Re: Bun support is now limited and deprecated

#494

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.

Here is him saying that in words that could be interpreted as ‘this is just an experiment’: https://news.ycombinator.com/item?id=48019226

Re: Bun support is now limited and deprecated

#495
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

They support Windows, which is many millions of lines of code not written by the current maintainers.

> They support Windows, which is many millions of lines of code not written by the current maintainers.

All of which was battle-tested on millions, if not billions, of devices over 40 years. The new Bun is effectively a different project than it was a month ago, with next to no prod use.

I have no problem having a dependency on a 40 year/billions of use software, I do have misgivings about a dependency on a project that has never been used in prod, and was only written last week.

Re: Bun support is now limited and deprecated

#496

Earlier quoted context omitted.

They support Windows, which is many millions of lines of code not written by the current maintainers.

Windows have a incredible degree of architectural coherence and design intentionality. It is far easier to understand some part of the various NT source code leaks than it is to understand Claude code leak

This comment is true on both points: Dave Cutler certainly knew what he was doing.

Re: Bun support is now limited and deprecated

#497
post #51

Earlier quoted context omitted.

I don't see any hypocrisy in the comment you are criticizing. The behavior they are criticizing appears to be vibe coding. How is rejecting something for being vibe coding "exhibiting the behavior" of vibe coding?

You aren't allowed to dismiss vibe coded software based on the slop vibes. It must be well-researched and human reviewed in order to have an opinion.

“Don’t like it – don’t use it, nobody owes you anything”, then the next thread “noooo, why have you stopped using it, you must support my slop”. Absolute cinema.

Re: Bun support is now limited and deprecated

#498

Earlier quoted context omitted.

You want the yt-dlp authors to review the entire post-migration Bun codebase? And what are you referring to as "behavior"?

Do you review your dependencies’ entire code?

I trust maintainers of my dependencies, I don’t trust Bun anymore.

Re: Bun support is now limited and deprecated

#500
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…

> I don't select my engineering tools because they give me a bad feeling - I select them because they do the thing I want them to. If Bun starts having more bugs and feeling like worse software, I'll stop using it. But I will base that on data -- not a feeling I have. Jarred has done a lot of impressive stuff with Bun, and it seems unlikely he would ship this rewrite if it didn't meet his quality bar - I am willing to see him out here.

I have a t-shirt signed by THE Jarred himself, how much are you willing to pay for it? Comes with a month of free Claude max subscription.

Post reply on HN