I feel like this is the core of the author's frustration.
Rust is a systems language. It's for writing tight fast C-like code but safely and with a much more powerful type system.
The facilities you need to do this are somewhat at odds with what you want for rapid iteration.
Seems like Rust was the wrong tool for the job.
Sure, but the problem is when you have a community around that tool that insists otherwise.
> From startups to large corporations, from embedded devices to scalable web services, Rust is a great fit.
Are these "systems"? FWIW "systems" does not appear on the Rust home page.
From wikipedia:
> Rust is a multi-paradigm, general-purpose programming language that emphasizes performance, type safety, and concurrency.
So... a systems programming language? x)
Rust -> move slowly and don't break anything
As someone who works in gamedev I can assure you C++ is same bad choice for 2 man indie project. In search of fast iteration times games have moved away from writing code in low level languages. Hardware for casual games is much bigger and faster than anything small team is able to make.
I'm pretty fast in Rust but not as fast as Go, mostly because Rust's type system and borrow semantics come with a higher cognitive load.
I find both to be faster than C++. Rust is faster because I have to worry less about blowing my feet off with memory errors. I can't think of anything to recommend C++ now that Rust exists.