Three years and you're not convinced. Not a good sign.

I'm here because I read "the book" over summer, made notes and began to write something using it, and... I'll probably give up my sunk costs, because I value my time and sanity much more.

I expected the borrow checking to be "the problem", but I understood those concepts easily. The book touches on generics, it seemed fine in print, but as soon as I was using a web framework, which is good way to experience quickly what the thick end is like, I found myself in the deplorable type system morass that many TypeScript developers create for themselves and their poor colleagues.

I'll try Go. I love the idea that Go has barely any features, barely changes, has one way to do things, and is very fast. And decent companies use it (the companies using a language is an important thing).

After more than two decades coding, I realise that simplicity and productivity are the thing, along with joy. Rust is absolutely not simple and not worth the productivity trade off for anything other than replacing worse languages.

I assume people love Rust because of where they've emigrated from.

P.S. Never creating a null can get you very far. In my experience, most problems come from the single mistake of returning null, or instantiating structs with nulls.