I think it's, in general, useful to differentiate the speed of code-writing as a new developer and the speed of code-writing as an experienced developer. The r

I think it's, in general, useful to differentiate the speed of code-writing as a new developer and the speed of code-writing as an experienced developer. The reality is that people have very little time to try out new languages, and have to rely on anecdotes about the long-term cognitive costs of things like this. My personal experience is that many of the seemingly more-onerous things about Rust end up falling away once the rhythm of programming sets in. This is likely similar to how the error-handling approach of Go looks onerous at first, but seems to be something that doesn't slow people down too much in practice.