Live data from Hacker News

I am worried about Bun

wwj.dev

291–300 of 368 posts

Re: I am worried about Bun

#291
post #229

Earlier quoted context omitted.

Saying that you “work on Bun” is such a radical understatement. I have my reservations about Anthropic, but I don’t see how Bun could go wrong with you at the helm. And I’m sure that you are putting the stability and funding of a larger organization to good use :) I’ve been a Bun maximalist since the beginning. Thank you Jarred!!!

Perhaps it could go wrong because he uses AI robots to generate responses to issues on claude code that are also generated by AI robots? Just bots talking to each other like moltbook. It shows a level of AI maximalism that is absurd, concerning, and funny. But probably par for the course for someone working at Anthropic. I can imagine being surrounded by people doing similarly foolish things only encourages the foole…

I don't really see the issue here. They are language models after-all and they work by talking. Whether it's one model talking to itself (i.e thinking/reasoning), or one model talking to another it amounts to the same thing.

Re: I am worried about Bun

#292
post #211

I work on Bun, and this post is confusing to me. Me personally and the Bun team continues to dogfood & make Bun better everyday. Our development pace has only gotten faster. Bun's stability has improved significantly since joining Anthropic. Here are some things shipping in the next version of Bun: - 17 MB smaller Windows x64 binaries [0] - 8 MB smaller Linux binaries [1] - `--no-orphans` CLI flag to recursively kill…

Hey Jarred, first of all, thanks. I've been doing backend JS since the first release of node and bun is genuinely the first really big improvement in terms of DX. It's an absolute delight to build glue and scripts with... Bun.* just seems to have everything I need. Bun.$ is revolutionary. etc. etc. I'm hoping to run a collection of backend services on it in the near future but it seems the general consensus is that there are still some gremlins holding it back (memory leaks, etc.)

Can you shed a little light on the recent giant rust based commits though? Are you guys moving away from zig? These kind of big curious movements and the spectre of giant LLM-based commits are not exactly confidence inspiring.

Re: I am worried about Bun

#293
post #229

Earlier quoted context omitted.

Saying that you “work on Bun” is such a radical understatement. I have my reservations about Anthropic, but I don’t see how Bun could go wrong with you at the helm. And I’m sure that you are putting the stability and funding of a larger organization to good use :) I’ve been a Bun maximalist since the beginning. Thank you Jarred!!!

Perhaps it could go wrong because he uses AI robots to generate responses to issues on claude code that are also generated by AI robots? Just bots talking to each other like moltbook. It shows a level of AI maximalism that is absurd, concerning, and funny. But probably par for the course for someone working at Anthropic. I can imagine being surrounded by people doing similarly foolish things only encourages the foole…

It's a little heartbreaking. The DX of Bun is legitimately amazing and perhaps even revolutionary (I say this as a long-time javascript backender). I'm all for LLM-based development velocity enhancement, but it does really feel like they are taking it too far and moving too fast.

Re: I am worried about Bun

#294

Why people use Deno and Bun over Node? I think it's neat that there are competitors for JS runtimes, but I really don't understand what advantages I'd get by swapping to one of these over Node. Bun has no REPL and worse JS engine, Deno is just Node with a restrictive, annoying permission system and no sqlite. Both claim better performance, but that only seems true in cherrypicked benchmarks, and in my tests (granted…

...try `bun repl` in your terminal

otherwise, bun has a big "batteries included" thing going on.

For instance,

- Bun.$ to run shell commands

- an entire redis client at Bun.redis

There are dozens of other examples like this

For rapid prototyping, complex glue scripts, etc. it's an absolute joy to work with. There is often no reason to pull in any dependencies to accomplish what you want.

Re: I am worried about Bun

#295
post #58

Earlier quoted context omitted.

"Profitable" is the wrong metric, really, it's whether it is sustainable - can development continue indefinitely given the current financial situation?

I'm thinking about your comment... It put many wheels to spin... Tldr; I think the don't care about what will happen to the company in medium or long term. --- Are any of those companies looking for stability or sustainability? I have the impression they are completely aware of the diminished return effects and they will explore the moment to the fullest of their capabilities promising even more absurd things when th…

I think there's also an idea that sustainability requires constant maintenance and improvement; but TeX is sustainable and it's approaching a limit function - it (plain TeX) gets no new features, but has very few remaining bugs.

Re: I am worried about Bun

#296

Why people use Deno and Bun over Node? I think it's neat that there are competitors for JS runtimes, but I really don't understand what advantages I'd get by swapping to one of these over Node. Bun has no REPL and worse JS engine, Deno is just Node with a restrictive, annoying permission system and no sqlite. Both claim better performance, but that only seems true in cherrypicked benchmarks, and in my tests (granted…

Started using Bun last year for some quick tests and it ended up fully replacing Node for any new projects after using it for over a decade.

I've reduced my dependencies 5-10x. Got full TS and JSX/TSX support with zero setup. Watch mode is instant. You can deploy a single binary.

I kept waiting for all the breaking issues people complain online but my experience has been nothing but positive.

Re: I am worried about Bun

#297
post #78
post #65

Earlier quoted context omitted.

> Now, even though their parent company does some shitty practices with their other software (claude code), it's a stretch to assume this will also translate into making Bun worse: Being worried makes sense but I remain optimistic about Bun. Can you point to any examples of a company with shitty practices buying one without shitty practices that didn't end up with the shitty practices diffusing through the newly-acqu…

I'm not the parent poster which is why I still stick to looking at the people... If you start seeing the people that created bun leaving Anthropic, then I'd probably start to worry. And I haven't seen any sign of that yet.

6 month earnouts..... wait until july

Re: I am worried about Bun

#298
post #276

> team ships constantly Why do people want this? Shipping constantly is how software breaks. You want tools that are good and stable, not constantly churning. I wish software developers would wake up to the idea that velocity is not a marker of quality.

Not shipping enough is how they die, too. It's hard to find a balance.

Not really.

Careful, focused work can easily sustain daily, or almost-daily, shipping. We've been doing it for decades without LLMs.

LLM-brain is pushing people into continuous by the hour shipping and it is absolutely unecessary and creating code at a rate that cannot possibly be kept up with in relation to quality, performance and security.

Re: I am worried about Bun

#299
post #211

I work on Bun, and this post is confusing to me. Me personally and the Bun team continues to dogfood & make Bun better everyday. Our development pace has only gotten faster. Bun's stability has improved significantly since joining Anthropic. Here are some things shipping in the next version of Bun: - 17 MB smaller Windows x64 binaries [0] - 8 MB smaller Linux binaries [1] - `--no-orphans` CLI flag to recursively kill…

I think velocity is a real risk to stability, dogfooding or not. That's what made me swear off the python transformers library. It's doubtful that LLMs will change that calculus for the better.

Re: I am worried about Bun

#300

I disagree with the overall premise: Before the acquisition, Bun had to figure out how to monetize at some point. Now, even though their parent company does some shitty practices with their other software (claude code), it's a stretch to assume this will also translate into making Bun worse: Being worried makes sense but I remain optimistic about Bun. Especially given the context of both of these different context: C…

I disagree with the overall premise: Before the acquisition, GitHub had to figure out how to monetize at some point. Now, even though their parent company does some shitty practices with their other software (Embrace, Extend, Extinguish, MS Windows), it's a stretch to assume this will also translate into making GitHub worse: Being worried makes sense but I remain optimistic about GitHub.

This is a joke, right?
Post reply on HN