Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bun support is now limited and deprecated

github.com

Post reply on HN
Print view View original

251–260 of 646 posts

Re: Bun support is now limited and deprecated

#251

Post by Kiro »

b40d-48b2-979e wrote: post #117
adamtaylor_13 wrote: post #80

We desperately need some new terminology to describe using LLMs to support development work. "Vibe code" has a strict definition but no one really cares. I have a really hard time believing that the Rust port was 100% "vibed" the way the original definition was laid out. It's a big slushy of emotions that I understand (both positive and negative) but it makes it so hard to actually tells what problem someone actually…

I'm using LLMs to assist my development and I'm measurably (in all the ways we engineers could possibly care about) doing better work faster. Studies suggest you aren't any faster and may in fact be slower. It's difficult to study such a new tech, but even optimistically, empirical evidence is only showing a ~3% gain in some domains. Writing code is rarely the limiting factor in our work.

There's no uncertainty here. Every day I ask myself how long something I did would have taken without it. The answer is always crystal clear. It's not hard or difficult at all.

Re: Bun support is now limited and deprecated

#252

Post by b40d-48b2-979e »

cdelsolar wrote: post #182
b40d-48b2-979e wrote: post #117

Earlier quoted context omitted.

I'm using LLMs to assist my development and I'm measurably (in all the ways we engineers could possibly care about) doing better work faster. Studies suggest you aren't any faster and may in fact be slower. It's difficult to study such a new tech, but even optimistically, empirical evidence is only showing a ~3% gain in some domains. Writing code is rarely the limiting factor in our work.

studies suggest nothing. i've released a massive number of features in the last year for several projects that i estimate would have taken me multiple years to put together in a much more mentally exhausting way.

Your drive-by comments are unwelcome. You can estimate all you want, but the data is collating, and it isn't within your worldview.

Re: Bun support is now limited and deprecated

#253

Post by truncate »

johnfn wrote: post #145
gpm wrote: post #98

Earlier quoted context omitted.

> 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.) On the flip side it's not on the yt-dlp authors to test Bun's new development process and see if it results in more segfaults, OOMs, security vulnerabilities, etc. In fact it would arguably be negligent to…

> It seems a bit unfortunate to me that they've apparently already intending to never support future releases instead of planning on re-evaluating in the future. On the other hand the yt-dlp developers definitely don't owe anyone anything. I think your final comment gets at it. If they said "OK, I am skeptical, so we're going to pause on updating to see how this Rust thing plays out" -- that sounds like a reasonable…

> Saying "because they vibe coded we are dropping support for Bun" sounds political.

I disagree that this is a political stance. People based on their experiences have formed opinions on whether they trust that model of development or not. Bun having taking extreme measure of going 100% in within a week is itself extreme positioning from their side which will likely result in extreme reactions because depending on who you are and your experience you'd bet on the fact that it may or may not work out.

Re: Bun support is now limited and deprecated

#254

Post by ozozozd »

egorfine wrote: post #210
cizezsy wrote: post #107

Earlier quoted context omitted.

I don't think refactoring 1M lines of code into another language within 7 days and merging it to master is responsible. I won't make my code depend on it.

It's not refactoring. It's LLM transpiled.

I think the correct term is *translopped*

Re: Bun support is now limited and deprecated

#255

Post by cheesefck »

egorfine wrote: post #210
cizezsy wrote: post #107

Earlier quoted context omitted.

I don't think refactoring 1M lines of code into another language within 7 days and merging it to master is responsible. I won't make my code depend on it.

It's not refactoring. It's LLM transpiled.

[dead]

Re: Bun support is now limited and deprecated

#256

Post by ozozozd »

johnfn wrote: post #152
hnav wrote: post #90

Earlier quoted context omitted.

a vibecoded rewrite right after being acquired is not political?

Is it so unthinkable to people on "hacker" news that someone might want to try a cool experiment like rewriting an entire repo into Rust?

Is it so unthinkable that people don’t want to participate in that cool experiment?

Re: Bun support is now limited and deprecated

#257

Post by truncate »

atonse wrote: post #234
kqp wrote: 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.…

>> 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.

Re: Bun support is now limited and deprecated

#258

Post by love2read »

b40d-48b2-979e wrote: post #149
therepanic wrote: post #111

To be honest, I share primeagen's view that LLMs handle translating code from one language to another quite well. As far as I know, they converted the languages file by file. This is what led to such a high volume of `unsafe` code. Although, in any case let's be honest, this is causing, and will continue to cause, various issues. I find it easier to live with this point of view.

primeagen's view He's a content creator on youtube, a celebrity, not a serious programmer.

Who cares what you think of someone else’s qualifications?

It’s just someone quoting someone to help ground their position.

What if it was a journalist writing about a security vulnerability then a programmer quoting them, would that count then?

Re: Bun support is now limited and deprecated

#259

Post by szmarczak »

dsherret wrote: post #212
szmarczak wrote: post #99

Earlier quoted context omitted.

Since when small vibe coded slop became the norm? Because there exists bigger vibe coded slop, it's no justification to have a smaller vibe coded slop.

One shotting slop is very different from iterating back and forth with an AI. Also, most of the AI work that's being done has been getting node compatibility tests passing with the help of comparing that to the Node.js code, which is something an LLM is very good at.

> One shotting slop is very different from iterating back and forth with an AI.

Bun is also iterating back and forth with AI. The rewrite only got popular because of bigger scope. The bigger the scope is, the more bugs there are.

> getting node compatibility tests passing

So does Bun.

> which is something an LLM is very good at.

Doesn't matter. The code those LLMs operate on is simple enough that any middle software engineer can do.

Re: Bun support is now limited and deprecated

#260

Post by tredre3 »

Jblx2 wrote: post #222
xmodem wrote: post #142

I see a lot of commentators in this thread who are aggressively critical of volunteer maintainers for making a decision about how to maximize the value of the free labor they donate to the world. And yet none have offered to volunteer their time to maintain a downstream fork or otherwise rectify the perceived problem. Strange.

Which "volunteers" are you referring to? Bun? yt-dlp?

yt-dlp, clearly. Bun has no volunteers (as of the rust rewrite at least, it's all highly paid SWEs and GPUs.)
Post reply on HN