Live data from Hacker News

Bun support is now limited and deprecated

github.com

531–540 of 646 posts

Re: Bun support is now limited and deprecated

#531

Earlier quoted context omitted.

It's not impossible, or even that hard to review the entire rewritten codebase. 10 engineers each reviewing 5,000 LoC a day for 20 days can do it. And that is being highly conservative with the estimate. A good chunk of the the code is probably highly trivial boilerplate one can easily skim over in minutes.

20 days is rookie numbers. I can get a million engineers to each review a single line and finish code reviewing the entire code base in a minute.

the code base was rewritten file by file, so parallelizing individual files makes sense, but lines is just BS

Re: Bun support is now limited and deprecated

#532

Earlier quoted context omitted.

Why is it so hard to believe that Jarred Sumner, a self-described "Thiel Fellow and a high school dropout", had values aligned with Anthropic's before Bun was approached for acquisition? It's not like Claude was an asteroid that crashed into Eden.

Wtf is your problem with high school dropouts exactly?

No problem.

Re: Bun support is now limited and deprecated

#533
post #525

Most people who use/used bun have never read bun's code. Then why does it matter who/what wrote the code? And to be honest bun's zig codebase (especially in the early days) was neither "clean" nor "idiomatic" but the tool worked and people used it.

> Then why does it matter who/what wrote the code? You trust for someones expertice.

like the one of Jarred-Sumner, whos responsible for the rewrite?

Re: Bun support is now limited and deprecated

#534
post #533
post #525

Earlier quoted context omitted.

> Then why does it matter who/what wrote the code? You trust for someones expertice.

like the one of Jarred-Sumner, whos responsible for the rewrite?

Claude is responsible for the rewrite.

Re: Bun support is now limited and deprecated

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

it's funny how the readme still says "written in Zig"

Maybe it should say "designed in Zig" because most of the work & thinking was done using that language. The rewrite has no such history.

Re: Bun support is now limited and deprecated

#537

Earlier quoted context omitted.

I don’t think changing from zig to rust suddenly means that don’t know what a certain file contains or how it works or how it relates to other files. It’s all the same just different syntax. Which, by the way, is why it looks ugly to rust developers. The devs wanted the code to look familiar to them. I do think they should have called this 2.0 though. Would not feel such a rush (1.3.14 has a few regressions, and no o…

> It’s all the same just different syntax. That reminds me of Chris Reigrut's story from https://thedailywtf.com/articles/Holiday_Smorgasbord

I don't know why but AI and LLMs seems to make people to lose basic sense of rationality. I didn't think we would have seen so many comments such as "It’s all the same just different syntax" after a full rewrite some years ago.

Re: Bun support is now limited and deprecated

#538
post #2

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.

ITS NOT VIBE CODED , JUST TRANSLATED .

It is vibe coded with a very good prompt.

Re: Bun support is now limited and deprecated

#539
post #75

This is about the rust conversion but that has not been released. > Due to foreseeable compatibility and security issues Hmm, Zig bun crashes plenty. I wish yt-dlp linked to detail on why there are foreseeable compatibility issues. Both projects have test suites, in an ideal world they would allow fast rewrites. Maybe they want to limit inflaming the situation, but if they have spotted some specific issues it would b…

They could at least wait a bit, test the new Bun for some weeks/months, have people read big chunks of the codebase.

It should be a major release indeed, and communicated as such, with full accountability of the migration beyond an “all tests pass”. A major tool should move slower, be tested longer, more thoroughly, since it’s used my millions.

It’s reminiscent of JavaScript world, where something is in beta for mere days (e.g. Expo’s short release cycle).

Re: Bun support is now limited and deprecated

#540

Earlier quoted context omitted.

[flagged]

Anyone who isn’t supporting using runtime rewritten by an LLM is obviously “doesn’t get it” and a luddite.

But in this case, the yt-dlp maintainers didn't actually evaluate the rewrite yet, they just declared they wouldn't support it, sight unseen.

Not really an argument on its merits.

Post reply on HN