I choose Rust for web development, the oldest running product I have is ~2 years old at this point.
Prototyping is slower but maintenance is faster. It's a trade-off.
I have a bunch of products and every once and then something needs fixing. When it's one of my node.js or python projects it's usually a bath of blood and I'm never confident I changed the right things.
With Rust I get a type error until everything is plugged in correctly - the only mistakes I get are logical ones.
TypeScript kind of gives you a similar experience but it has more escape hatches.
If you want to close all the exceptions and make everything type safe it will take you a similar amount of time as writing Rust code.
The end result is that when I see a TS codebase I can't trust it: I might have written some unknown / any and there is a massive gap in types. This negates any benefits I get from type safety.
In Rust this is not possible, as long as you're using safe dependencies (which you most likely are if you're writing a web service in Axum).
Prototyping is slower but maintenance is faster. It's a trade-off.
I have a bunch of products and every once and then something needs fixing. When it's one of my node.js or python projects it's usually a bath of blood and I'm never confident I changed the right things.
With Rust I get a type error until everything is plugged in correctly - the only mistakes I get are logical ones.
TypeScript kind of gives you a similar experience but it has more escape hatches. If you want to close all the exceptions and make everything type safe it will take you a similar amount of time as writing Rust code.
The end result is that when I see a TS codebase I can't trust it: I might have written some unknown / any and there is a massive gap in types. This negates any benefits I get from type safety.
In Rust this is not possible, as long as you're using safe dependencies (which you most likely are if you're writing a web service in Axum).