The question here is -- are you "productive" because you write _good_ code faster, or because the language allows you to _not think_ about certain aspects of de

The question here is -- are you "productive" because you write _good_ code faster, or because the language allows you to _not think_ about certain aspects of design and just postpone issues to the future (or GC). OP wants to be fast and "productive", but forgets that in systems programming your first priority is good design and solid implementation. This is because _other_ components will be relying on your code to do their job. It pays to go extra step and make sure your component is properly written. Rust offers more than any other systems language to help with that.