Can you think of any cases where he might be right? How often do you hit, for instance, "This code cleanly fit its original construction, but now I have to add some complexity for new cases, and Rust is making that harder?" Put another way, once you're familiar with the borrow checker, how often do you find yourself or your teams fighting it?
> 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
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.
> Rust’s way of managing memory is unique and clever. Unique and clever are generally seen as good things, but in software development they usually lead to difficulties with long-term maintenance, among other issues
The citations he gives are
1. a stack overflow post
2. a blog post (by an author I respect, but still)
I don't think that this alone proves his point. Even if we ignore that aspect of things, Rust is by far the easiest programming language I've ever had to do long-term maintenance on. This is specifically due to the guarantees.
So when I read the above, I see a very general argument, and my experience contradicts it here, so I don't really agree.
I am also, of course, incredibly biased.