-
Unused code is one issue. A project called Buz[1] found over 11,000 lines of dead code from the Rust port.
[1]: https://github.com/jazzzooo/buz
-
AppSignal
AppSignal knows why the f*#k it crashed. Stop vibe-debugging. Every exception, every backtrace, grouped so you see patterns, not noise.
-
That's a fair criticism... they move slower but mostly because they were the first. They would have to build a new Server and Request/Response primitives from scratch, or deprecate what they already have, or somehow shoehorn the existing types into the new ones.
They do seem to have just merged in support for Web Workers though, which I've been following for a while: https://github.com/nodejs/node/issues/43583
So I don't think they're opposed to standardising, but it's trickier when you have some past cruft built up. Lets not forget that the fetch() standard was built for browsers, and is a bit of a stretch to make it work on servers at all. You have to diverge from the fetch spec to even make it make sense in a server environment (with things like Cookies handling off the top of my head).
-
> 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.
Personally I expected the release cadence was going to go through the roof, but instead it flat lined.
