[IshKebab]

Performance isn't Rust's only feature. I would say it isn't even its most important one.

I've written websites with Rust simply because it's a sane modern language with few "gotchas" and a type system and borrowing system that allows you to eliminate huge classes of bugs (not just memory errors!)

That said I think the Rust web ecosystem is not super mature (especially client side) and most web frameworks use `async` which is one of the sketchiest parts of Rust IMO. So I don't think it would be entirely unreasonable to use something else. Especially Typescript, for the SSR/isomorphic apps.

[Nextgrid]

How does this compare to let's say Java, which has both type-safety and a mature web ecosystem?

[IshKebab]

Java's type safety is far far weaker than Rust's and it doesn't have the borrowing system, so you don't get the "if it compiles it works" experience you do in Rust and (so I'm told) Haskell.

It does have a very mature server side web ecosystem so it's a perfectly reasonable option. I've written Java web servers before and it was fine.

I wouldn't use it for client side though (a la GWT). Debugging nightmare.

[gorjusborg]

Fair enough.

I guess what's implicit in my attitude is that I think Rust introduces cognitive load that other (especially garbage-collected) languages do. There has to be enough of a win gotten to offset that. I used performance as the most likely reason I could think of.