Okay thanks for the insights. Learning curve may reduce the available engineers (at least for a bit) but my concern is about whether the PL's premises are holding up in real world usage, which it sounds like (for you and other commenters) it has.
Re:Rust's Complexity Problem – A Warning
by steveklabnik on Tuesday March 17, 2020 @04:47PM
(#22610227)
Ah yeah. So I wrote this comment three weeks ago: https://news.ycombinator.com/item?id=22411324
And as of earlier today, it's no longer just the way bytes are stored on Dropbox, but now every file sync too https://news.ycombinator.com/item?id=22595782
It seems to be holding up! Still relatively early days.
> Put another way, once you're familiar with the borrow checker, how often do you find yourself or your teams fighting it?
Extremely rarely, if ever. It yells at you, you go "oh yeah, oops" and fix it, and move on with life.
But, I should qualify that's mostly personal experience and what I hear from other folks generally and other teams at work; my team at work doesn't really write Rust, our main codebase is in Typescript and Go.
I just saw this thread by the ex-CTO of Chef, it matches my experiences here: https://twitter.com/adamhjk/status/1239989909714173952