Others mention the smoothness of Serde. I also really enjoy using sqlx, and the wider tooling and crate documentation makes it a pleasure.
I do really miss the compilation speeds of ts, and even with a lot of fiddling it’s hard to get close to but the borrow checker and dev speed has almost caught up at this point if it wasn’t for the compile times. CI/CD still 5-8 minutes for us even with a lot of caching etc. Lack of enterprise resources is also a little tough though I find C# and F# resources good analogues.
Perhaps my favourite little benefit which I really regret being without on ts services is the ability to clone a repo and then use your own copy as the crate. Allows a lot of debugging power, and allows you to run with your own patches while they’re still getting accepted into the crate. Honestly my favourite feature of crates.
Would I use Rust if I had to start a business from scratch? Maybe. I joke with a friend I’d probably prototype microservices in TS then migrate the high traffic ones to Rust. The memory footprint is great but rarely a business requirement. The volume it can handle might be?
I kind of feel like there's a disconnect here between people who write software solely for work & to solve an engineering problem vs people who like it as a hobby.
I have very little interest in using Rust for webdev, but I'm excited to see what people having fun with it will come up with.
I use Go professionally and would most likely choose that if I had to do any new “serious” web dev project. But the Rust eco system has come a long way. Plus, the borrow checker aren’t really that tedious once you get use to it. At that point you get a lot of benefits!
You can inject web::Data<T> into your handlers for any dependency you'd like : database pools, config objects, in-memory caches that you populate from another thread.
Serde makes request and response marshalling a breeze.
The websocket support is great too.
We're using it for a couple of high traffic websites now.
The ecosystem needs better SQL tools. Diesel is too ORMy, and SQLx has rough edges around connection pooling. But these aren't show stoppers, and it'll get better.
