[closeparen]

Memory safety is the main thing though, and people were not normally practicing web development in C.

For concurrency safety, there are a number of approaches from functional programming/immutability, to the actor model, to even PHP's shared-nothing architecture.

And then there's the whole area of type safety, fancy type systems, dependent types, etc.

Rust doesn't seem to be a particular standout for web application correctness in the same way that it is for systems code (where memory safety issues are indeed a huge deal), although you could certainly do worse.

[dhzhzjsbevs]

Wasn't most of Google and eBay written in C/C++?

Most of the webs applications were written in C/C++ pre PHP days.

[saghm]

I think the original question here was asking about frontend since this post is about using Rust with web assembly as an alternative to JavaScript. There's no need to use web assembly to use Rust on the backend, nor is there any reason why you couldn't use JavaScript on the frontend if you were using Rust on the backend. As much as I love Rust and prefer to avoid writing JavaScript, I think the arguments for using Rust on the frontend are a lot less clear right now given the hoops you'd need to jump through. If wasm ends up getting proper access to the DOM, that might change, but I'm out of the loop and have no idea if there's any planned timeline for that at all, let alone when that might be.

[icedchai]

Many folks were using Perl CGI scripts, or ASP (VBScript.)