2 ms·

Isn't Bun too raw? It's built with Zig, which hasn't even hit 1.0.

• laxis96 2y ago
  Probably had to stay in the oven a bit longer... Jokes apart, Zig is moving forward a lot which is why it's not 1.0 yet, but it doesn't mean you can't write safe and performant applications right now. Zig is also a rather simple and straightforward language (like C) and has powerful compile-time code generation (like C macros, but without the awful preprocessor).
  • oblio 2y ago
    I'm more worried about compilation or stdlib bugs. In theory you can do lots of things with lots of things, but in practice there are all sorts of hidden limitations and bugs that tend to be noticed once a software product is past 1.0 and has been out in the wild for half a decade or more.
• jokethrowaway 2y ago
  You still get segmentation faults. My biggest complain with bun is not having enough safety. If you use frameworks written for node memory usage is very high and performance is meh. If you use frameworks written for bun they smoke anything on node. I'd definitely move over, just to get rid of the whole TypeScript / cjs / esm crap, but: 1. frontend support is poor (next.js / solid.js - I can't run anything fully on bun) 3. I still need to rewrite my backend app from a node.js framework to a bun one 4. for backend development the javascript ecosystem is losing the crown: if I wanted something safe I'd just write it in Rust (TS allows any random developer to write crap with any in it and it validates), if I'm doing something AI related I'd probably need python anyway and fastapi is not half bad
  • tossandthrow 2y ago
    We use Bun in production for the entire stack and has done since v1 - only with minor hikups, that all trvivially has been fixed. DX is great! We use vite react ts, yoga, and prisma.