|
|
|
|
|
by gorjusborg
1367 days ago
|
|
Rust in a web dev shop would be a huge premature optimzation smell for me. Most public web apps are expected to be up pretty much all of the time, which today, means cloud hosting and horizontally scalable architecture. In such a setup, I don't see how squeezing every last drop of performance is worth it. When I can just change a number and get more instances, choosing the language with higher cognitive load is going reduce any cost savings due to lower resource usage. Doing something as mundane as writing text to a socket just doesn't need to perform all that well. Developer effort costs more than the CPU/memory. |
|
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.