The most problem with tech is fast change rate. It leads to a troubles with devising good ways to teach. You know, if we look at any teaching process, we'll see that people teach other people by the way they'd learnt themselves. It comes naturally to any people, and therefore we could read that BASIC is the best language for novices: because those who recommend BASIC learn how to code with BASIC.
Normally this process of creating curriculum works, generation of professors after generation distill teaching methods. But it does not works with modern tech. If we tried to keep in the curriculum all the stuff we learnt in a college and than add some more, than in a mere 20 years we might come to a situation when students needs 10 more years to get a degree. So we need to throw things out, and no one really know how important rejected bits of knowledge. Because knowledge is not a state of mind, it is not a bunch of bits, it is a process evolving through education and experience. So to replicate knowledge of a person we need to replicate process from the birth.
First years of human life backed up by thousands years of parental experience, and they generally work. But the book about Rust was written a several years ago. Than it was rewritten. Maybe a decade more and it come to a state when ownership and borrowing is not difficult at all. There is nothing inherently complex in ownership and borrowing, it just our past experience gets in a way of understanding them. All we need is to create RASIC -- a rust version of BASIC, -- and teach kids to program in RASIC with an intent to introduce them Rust later. Then the next generation would be unable to understand our troubles with ownership and borrowing, they would think that C rules are dumb and they need a specially wicked creative mind to invent them. They would see C rules as we see Brainfuck: someone did his best to invent a language to make things difficult.