It is true for most web apps that are just moving data between a database and HTML.
Rust has features for maximizing performance and optimizing memory usage, but for a lot web apps JS or Golang can be efficient enough.
Rust has features for safely working with large projects and complex multi-threaded code, but for web apps simple request-response processing may be good enough.
On the front-end only JavaScript can touch DOM or communicate with the rest of the world, so all your Rust will only be delegating work to JS. That's a pure overhead, unless you have a lot of other computation to do.
Rust is still awesome for lower-level networking infrastructure (servers, proxies, etc.) and tooling (e.g. log parsing and stats, compression, image processing).
Rust can be beneficial for web services that are compute heavy or process large amounts of data (e.g. working with map data) and tasks that need speed and low latency (e.g. video conferencing back-ends).
Rust has features for maximizing performance and optimizing memory usage, but for a lot web apps JS or Golang can be efficient enough.
Rust has features for safely working with large projects and complex multi-threaded code, but for web apps simple request-response processing may be good enough.
On the front-end only JavaScript can touch DOM or communicate with the rest of the world, so all your Rust will only be delegating work to JS. That's a pure overhead, unless you have a lot of other computation to do.
Rust is still awesome for lower-level networking infrastructure (servers, proxies, etc.) and tooling (e.g. log parsing and stats, compression, image processing).
Rust can be beneficial for web services that are compute heavy or process large amounts of data (e.g. working with map data) and tasks that need speed and low latency (e.g. video conferencing back-ends).