3 ms·

I think the specific scenario the author is talking about, ie a very large codebase providing some important infrastructure (Azure storage) with a relatively st

I think the specific scenario the author is talking about, ie a very large codebase providing some important infrastructure (Azure storage) with a relatively stable core is one where the costs of Rusts complexity start to be outweighed by the benefits, and Rust starts to make a lot of sense. Where Rust’s complexity does matter is in projects that prioritise getting developers on boarded and implementing new features as fast as possible, such as user facing web services. These things probably would not benefit from Rusts correctness guarantees in a meaningful way, but stand to lose by making it harder for developers to get productive.

jamesfinlayson 4y ago
> Where Rust’s complexity does matter is in projects that prioritise getting developers on boarded and implementing new features as fast as possible Agreed, and I think unfamiliar developers implementing new features as fast as possible is also much more likely to result in hacky/make it work code than throwing a Java developer at a C# project or similar.
eternityforest 4y ago
Isn't that exactly where you would need Rust the most, to prevent new devs from doing damage? Presumably one is going to make mistakes on an unfamiliar codebase, so they would want strong correctness guarantees to help them, especially if the codebase was full of footguns and undocumented nonsense.