/s ? Bun is not yet (ever?) compatible with Node. I'm sure if Node JS could trim the fat with breaking changes they'd be fast too
replyHonest question, what isn't compatible? Where I work we've simply replaced node with bun across a lot of overcomplicated + crappy projects, and on my work+personal computers I alias bun/bunx to node/npx with seemingly no issues at all
replyI expect bun to run almost everything that node runs these days. They have an extensive test suit to ensure that.
replyEven the complicated NextJS runs with Bun: https://nextjs.org/conf/session/nextjs-bun
Do you have a source for your claim?
Maybe if you start from scratch with a new project, but when migrating an old project it's definitely not a drop-in replacement. I try once or twice per year, but it's not worth the effort when the upside isn't that big.
replydeleted
replyIn my testing Bun wasn't much faster most of the time, usually on par for all non-IO related stuff, and there were some cases with scheduling where Bun was noticable slower.
replyThey should the unexpected and vibe code node to zig. Or Odin for the kicks.
replyI see no reason to leave node in what concerns JavaScript runtimes.
replythey should rewrite their whole stack by AI from one language to another language, it seems fun.
reply