Sure, if by "smaller issues" you mean a likely redesign of large parts of the codebase. Think of it like writing C code without bothering to free any memory. I

Sure, if by "smaller issues" you mean a likely redesign of large parts of the codebase. Think of it like writing C code without bothering to free any memory. In C having to free allocated memory manually dictates how data structures are built and how your program flows. Often you have to keep track of extra state in order to free your memory at the right time and if you don't have this in mind from the get-go you're going to write code that leaks a lot of memory or doesn't work. The same is true for rust, but instead of the code leaking or not working it doesn't compile. If you turn those checks off with unsafe you're essentially stuck with an improved C that's just as difficult to prototype in. Systems programming languages are simply not designed for fast prototyping, instead focusing on fast and in rust's case correct code. A GC, dynamic typing, high level library, etc. all help you prototype faster but you're not going to be able to use them to write an OS or a web browser.