| ▲ | aypineau 3 days ago | ||||||||||||||||||||||||||||||||||||||||
I'm really skeptical about this rewrite I chose to adopt bun about a year ago, and I've honestly lost count of the number of issues i've submitted and the amount of time i've wasted dealing with them. If I had to make the choice again, I would probably stick with node and pnpm for serious projects We're constantly being sold on promises of -XX% ram usage, but in practice, it's often builds randomly failing for no apparent reason, memory leaks bringing applications down, and instability that ends up costing far more in engineering time than the resources saved That's why i'm worried that bun 1.4 could end up being a step backwards, once again putting into question the small amount of stability we've managed to achieve so far But I still strongly believe the project makes a lot of sense, and I genuinely think these issues can be solved by 2028, if the project keeps its focus on stability instead of another SDK for SQL, web sockets, image compression, or whatever comes next | |||||||||||||||||||||||||||||||||||||||||
| ▲ | owebmaster 3 days ago | parent | next [-] | ||||||||||||||||||||||||||||||||||||||||
> But I still strongly believe the project makes a lot of sense, and I genuinely think these issues can be solved by 2028, if the project keeps its focus on stability instead of another SDK for SQL, web sockets, image compression, or whatever comes next If you check the maintainer X, he's asking Claude for what features to implement next. Not only stabilizing isn't the priority, even the features implemented are random. | |||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||
| ▲ | hn_submit 3 days ago | parent | prev [-] | ||||||||||||||||||||||||||||||||||||||||
There's a lot riding on this. If the Bun rewrite fails it could lead to the U.S. and global financial system collapsing. Yes, incredible, but true. | |||||||||||||||||||||||||||||||||||||||||