About Rust in Webdev
The Rust-for-web ecosystem is sporadic. Sometimes you can find what you need, and in 99% of cases it will have version 0.x. “We use beta, because it's better than nothing” - it’s 100% about Rust right now. I wish I could say something better.
Looks like webdevs are not interested in wonderful languages, they are just looking for the shortest and the most simple solution they can find. It's depressing, but it's true.
Without any doubt, I sincerely think that the best language for API is still Rust. But what is our choice of frameworks? Forever 0.x Hyper, forever 0.x Rocket, that's all. Please don't even start with Actix - I hope this zombie will finally die soon. My only hope is that The Rust Foundation will acquire enough attention from bug tech to change the trend and improve Rust positions in webdev.
11 comments
[ 5.0 ms ] story [ 38.0 ms ] threadWhy is this problematic?
It’s not going to solve every problem and it never will.
I'd guesstimate 99.9% of web developers have no experience with native non-GC development. Asking them to embrace non-GC is a big ask when GC is not a performance bottleneck for common cases.
Save Rust for serious apps by elite teams. You don't need Rust for average Joe web services that do little more than ferry data around.
Rust gives us a nice type system and performance, in an enjoyable package.
We certainly don't need it (well, maybe in a single service), but it's our choice. The decision was largely Go vs Rust, but again, Go just didn't offer enough to us.
I agree though, a GC doesn't prevent us. Ours was a language choice, not a performance/GC choice.