Comment by Tade0
3 years ago
My take is that it was always about expanding the pool of people capable of writing safe code, thus making it cheaper.
I spent most of my career in front-end, where such considerations are way down the priority list, but even I was able to produce something in Rust that compiles.
That being said I never understood why would anyone want to use this language for web development - most problems are solved in that space, so if you're not out to tackle tje unsolved ones, it might not be worth it.
> That being said I never understood why would anyone want to use this language for web development
On the backend, at least, Rust would be a significant improvement over Ruby, for example, once a business has gotten past the initial prototyping phase. I've spent years in Ruby development, and the duck typing makes refactoring a production system scary and drama-prone. No matter how carefully you proceed, there will be gaps in test coverage, and you'll regularly see new bugs in production from the refactoring work that would never happen in a typed language. I would gladly work in Rust over Ruby in a web development context. (Although my preferences lean towards Rust, there are no doubt many other typed languages that could do a good job here as well.)