They were pleased to be faster than Go in the "Hello World" benchmark, but unfortunately, they lag behind Node.js and Deno in complex real-world workloads.
Bun 1.4 Rust rewrite is not looking good?
61–70 of 153 posts
Re: Bun 1.4 Rust rewrite is not looking good?
#62What is the right recommendation at this point for a Node alternative? Deno?
Re: Bun 1.4 Rust rewrite is not looking good?
#63Earlier quoted context omitted.
What's wrong with just using Node? It's stable, has a good (and growing) standard library and has enough backing to be self sustaining. edit: There's also nub which is built on top of Node.js and removes some rough/legacy edges: https://github.com/nubjs/nub
Node.js is virtually the only platform not supporting the Fetchable convention: https://github.com/nodejs/node/issues/63096 https://fetchable.org/
Re: Bun 1.4 Rust rewrite is not looking good?
#64Earlier quoted context omitted.
> The bun rewrite is looked to as proof that this sort of full-throttle vibecoding is the future of software development To who? You? > To prove that, a proper release is needed For who? Who is trying to prove what? > It's Jarred that keeps saying it'll be released tomorrow There's no official blog... he's just rambling on x? > Github insights for the last week That's the problem with the rest of your post. Bun is no…
None of that makes any sense whatsoever.
Re: Bun 1.4 Rust rewrite is not looking good?
#65This reads as another weirdly personal attack against Jarred for slighting a technology stack the author prefers, citing the even weirder personal attack against Jarred written by Andrew Kelley as the sole source to justify their "biggest worry", code quality. Idk why people have become so invested in this.
Re: Bun 1.4 Rust rewrite is not looking good?
#66Earlier quoted context omitted.
> It's not being shipped. What are you talking about? I'm running 1.4 canary (the Rust rewrite) right now. λ bun --version 1.4.0 Hope that helps.
> What are you talking about? I think GP was pointing out how bun's release cadence stalled and the project is going nowhere at the moment. https://github.com/oven-sh/bun/releases The project was pretty healthy up to 1.13.14, but since may they stopped shipping anything. That's quite odd for a project that just went through a major rewrite and is lauded as being developed primarily by LLM coding assistants. Personall…
Re: Bun 1.4 Rust rewrite is not looking good?
#67I'm still waiting for someone to bring forth some reproducible stats and state something along the lines of "I did a comparison of Bun 1.3 vs 1.4, and found these user-affecting issues in the latter which are not in the former".
Re: Bun 1.4 Rust rewrite is not looking good?
#68Bun has been nothing but amazing wins for me, and I really like what it enabled me to do. Two examples: - I have a couple of projects that handle images. I was including Sharp, but since these are side projects in a small VM, often a redeploy that recompiled Sharp just crashed the full VM (out of memory). Bun includes Bun.Image[1] natively, which is built around Sharp's API, so swapping Sharp out was very easy, and n…
I also use Bun.Image to collect image size and metadata, and also to generate low-quality image placeholders. Works great. Have you tried 1.4?
Re: Bun 1.4 Rust rewrite is not looking good?
#69Earlier quoted context omitted.
> It's not being shipped. What are you talking about? I'm running 1.4 canary (the Rust rewrite) right now. λ bun --version 1.4.0 Hope that helps.
> What are you talking about? I think GP was pointing out how bun's release cadence stalled and the project is going nowhere at the moment. https://github.com/oven-sh/bun/releases The project was pretty healthy up to 1.13.14, but since may they stopped shipping anything. That's quite odd for a project that just went through a major rewrite and is lauded as being developed primarily by LLM coding assistants. Personall…
Re: Bun 1.4 Rust rewrite is not looking good?
#70This reads as another weirdly personal attack against Jarred for slighting a technology stack the author prefers, citing the even weirder personal attack against Jarred written by Andrew Kelley as the sole source to justify their "biggest worry", code quality. Idk why people have become so invested in this.
People _really_ don't want there to be success stories for llms and they will go through all lengths to discredit and disparage folks successfully exploring the space.