Hacker News new | ask | show | jobs
by CuriouslyC 340 days ago
Honestly, I was bullish on Deno back in the day, but I don't see why I'd use it over Bun now.
2 comments

Less segfault, improved security / capability model
If the drive is towards greater performance by leveraging native code, at what point do we just bypass the JavaScript runtime abstraction and build directly with a language like Rust?

The ecosystem seems to have hit a critical mass for web development. You now have incredibly mature and production-ready frameworks like Actix and Axum, along with innovative ones like Warp and Tide, providing everything you'd expect from routing and middleware to templating and native JSON handling.

There are crates for everything, like for databases, there's powerful options like sqlx for fully async compile-time checked queries or Diesel for a feature-rich ORM, so it feels like all the pieces are there.

If you want to use rust, and it fits your use case, then use rust. Same as with any language choice if it’s the right thing for you then go ahead.

I have a few million lines of existing TypeScript so will keep using JS runtimes for the foreseeable future.

As a Bun user I don't really get segfaults anymore.
I've written C for years. The only time it is safe from crashes is when the code doesn't churn and has consistent timing between threads. bun has constant feature churn and new hardware it runs on all the time providing novel timings. It is very unlikely going to be crash free any time soon.
Just got one today! But yes it is better.
The security model is very underestimated imo, it will be very evident when more bun projects reach production and not experimental.
I have yet no reason to fight IT and architects for having anything besides node on CI/CD pipelines and base images for containers.