Live data from Hacker News

I am worried about Bun

wwj.dev

41–50 of 368 posts

Re: I am worried about Bun

#42
post #39

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…

> Before the acquisition, Bun had to figure out how to monetize at some point. I think it is insane that people got into a situation where they had committed to a javascript runtime that had to "figure out how to monetize at some point". It is also bizarre that some people are still hopeful despite it being acquired by one of the most enormously unprofitable companies in the most enormously unprofitable sectors of ou…

I know people say it is unprofitable but I wonder if there is a way to verify it is truly is. I will not say any details but I worked for a giant company which was barely making money YoY but somehow the bonuses for heads were bigger and bigger given a proxy metric related to profit.

There are way too many ways companies arrange to pay themselves and never be profitable to avoid taxes.

Re: I am worried about Bun

#43
I made this exact same decisions (bun -> pnpm) for similar reasons, mostly bc I didn’t like how haphazardly a core part of the stack was being vibe coded. Too many changes too quickly for something that’s supposed to be stable

Re: I am worried about Bun

#44
post #14

> Will we see issues start popping up in Bun that make it seem like the team doesn't even dogfood their own product? I don't know, but I'm not sure I want to continue using it just in case. I sympathize with the general premise. The reaction to move away seems pre-mature though. It sounds like `bun` is still performing just as well as before, and this sentiment isn't based on concrete changes. I also wouldn't expect…

Disagree, you definitely don’t want to be looking back saying “hm I knew it, I saw the signs, should have trusted myself”

Plus it’s not a huge lift right now

Re: I am worried about Bun

#45

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…

Nope. The need to monotize and the fact that an acquihire cost some money is exactly why relying on a specific runtime is where people should have concern.

Re: I am worried about Bun

#47

Regardless of Anthropic/ClaudeCode, PerryTS[1] looks like a very promising competitor to Bun. [1]: https://github.com/PerryTS/perry

This is cool! But AFAIK bun promises to be a one-stop-shop for all your JS/TS dev needs, while Perry is "just" a compiler from Typescript to native executables.
Post reply on HN