I really hope he doesn't fall into the trap I did when starting out with rust. I came into it with the perspective of an application programmer and I quickly became salty when my knowledge didn't translate smoothly into rust code. "Fighting the borrow checker", for me, was simply a clash of philosophies. My way of thinking versus the rust way of thinking.

The central issue, for me, is that with rust you MUST understand the memory model completely in order to be productive. You cannot wing this, you cannot assume anything. I was not used to this being an application programmer and this lead to the root of all my suffering. Once I wrote down all the borrowing rules and deeply thought about it, I finally became productive in the language.

I see the author shows symptoms of not understanding the memory model. His code proves it. Instead of being angry, he should try to view rust with an open mind and ask "why did they design it this way?". Be curious, create experiments, probe the rust semantics, master the borrow checker. There are rewards to be had for those willing to push through the pain of integrating new knowledge.