You just seem to have missed the point the author was making. I will try to clarify it: when you find out that a decision you made early on didn't pan out and y

You just seem to have missed the point the author was making. I will try to clarify it: when you find out that a decision you made early on didn't pan out and you're forced to change the lifetime of some data, this will incur major refactoring in Rust and that will cause you to lose a lot of time. It's nearly impossible to avoid mistakes like this, not because you don't know Rust enough, that's almost completely irrelevant... it's because you just can't predict the direction your design will go to after many iterations and changes in requirements, which are unavoidable in the real world. Replying to that with "Rust is easy to learn" just makes it sound like you didn't even understand what you're trying to reply to.