Lifetime issues are not really relevant in a classic web backend context, since you generally just pull data out of a DB and return it to a web request, or the other way around. You generally don't have to share you data structures.
I do agree though that the tooling is very immature compared to other ecosystems, and Rust is generally quite boilerplate heavy and slower to develop.
It can still be a good choice if you need really high performance/low resource consumption - or you are going for high correctness and robust error handling.
But for most web backends Rust won't make much sense.
(I say this as someone who even writes web frontends with Rust via wasm, where it is even less optimal - mainly due to the high compile times)
Do you have any examples of the sort of front end work your doing with Rust? I've been toying with an idea using Rust but I haven't started really working on it.
I do agree though that the tooling is very immature compared to other ecosystems, and Rust is generally quite boilerplate heavy and slower to develop.
It can still be a good choice if you need really high performance/low resource consumption - or you are going for high correctness and robust error handling.
But for most web backends Rust won't make much sense.
(I say this as someone who even writes web frontends with Rust via wasm, where it is even less optimal - mainly due to the high compile times)