I've never used bun on production for this very reason. But nevertheless, tens of thousands of people and businesses do.
And I'm not sure how you're responding to my comment. The parent said "this is a marketing stunt" derogatorily, as if it's slop that doesn't work. This is already the canary build, it's more stable than the current stable, and is actively in production products in wide use.
The parent is objectively wrong, whether or not I personally use Bun.
Jarred, reasonably and publicly, did not expect a 1.2 million line rewrite to finish, fix a hundred bugs, and have no noticeable regressions in 11 days of experimenting.
If the majority of those are at an FFI boundary to a language without lifetime analysis, I don't really see how they could be fixed without rewriting all that downstream software?
I mean, case in point. (One of?) Zig's largest adopted projects who was donating $60,000 a year made by a contributor that worked directly with Andrew... Was not "stinky" engineering.
If Bun can't get it right starting in 2026 with all of Zig's tooling and someone who worked on the language, what hope does my random team have?
Especially when we could, instead, use Rust. With a larger community to boot.
What? Do y'all even try it before saying things like this?
I use it primarily as a replacement for tmux to do terminal stuff, not use agents. It's awesome. It worked out of the box, has actually good, working mouse support, quickly ships fixes, and the defaults are sane with obvious behaviors represented in an intuitive TUI.
Yes, this is one of the hacks they use that are fundamentally inaccurate due to confounding variables like bathtub curves and different issues causing early failures and long-term failures...
Because, otherwise, they would need to run those drives for years and years with reasonable cycling and read/write pressure to report accurate numbers based on real world failure rates in real conditions.
If they want to avoid confounding variables to real world use, this could take years. Nobody wants to wait years after an innovation to sell their product, so they develop ways to speed up the testing and get a number.
A machine that presses a keyboard switch 500 times a second for several days straight is obviously not indicative of someone actually using the keyboard. But it'll get the "absolutely beat the snot out of it" number, which is usually good enough for marketing.
Wow, you have the patience of a saint. It seems you have almost nobody actually engaging in discussion and instead trying to nitpick and play word games.