3 ms·
I love Rust. But I don't recommend Rust for this kind of stack - only because Rust's ecosystem is not that stable. I swear rust has some of the fastest iterati
by preommr 3y ago
I love Rust.
But I don't recommend Rust for this kind of stack - only because Rust's ecosystem is not that stable. I swear rust has some of the fastest iteration, with sometimes really complicated setups out of any mainstream language. There's always some nightly build, some feature flag, some cargo setup that often gets in the way. Just consider that Axum here is only two years old. Built on top of and heavily tied with tokio, which is really popular, but no guarantees as the defacto solution moving forward.
I'd say anything else ts, python, sigh even golang would be better alternatives.
- stmblast 3y agoHere's to hoping Rust's ecosystem becomes more stable in the future! I'm very much looking forward to things like generators/coroutines (or whatever they're called now) once they're made stable as well as async traits and whatever makes the Pavex framework able to be used on stable Rust.
- pie_flavor 3y agoFull-time rust developer here. We have never experienced instability of any form outside of what instructions the WASM target supports; statements like this tend to conflate 'what's shiny and new' with 'what works'. Code written yesterday will work tomorrow, and that's all that matters; pick the most popular thing by download count and stick with it and you will have zero problems. Nightly unstable features are best worked around by not using them, and everything else related to 'cargo setups' are caused by not reading the instructions carefully enough. Funny that you then compare to typescript i.e. npm, which is infamous for actually having this problem.