<i>&gt; 3-4 months into programming Rust and you may just be getting past the phase where it takes you 10 minutes of fighting the borrow checker to get relatively simple code to compile.</i><p>This exactly is why I can never get past the first couple weeks of playing with Rust. Every few months I revisit it and every couple weeks after that I put it aside again.<p>When I was first learning C++ I spent a huge amount of my time inside the debugger trying to figure out why a pointer wasn&#x27;t ... pointing. There was always a reasonable explanation that way my fault and if I had just understood what my code was really doing I would have coded things right and it wouldn&#x27;t have crashed.<p>Now we have Rust that essentially takes away that entire problem. Just wipes it out by way of a clever compiler. Only now we substitute this same learning curve &quot;debugging&quot; the compiler rather than debugging memory space. <i>(Probably a better trade-off in the long run. Rust sort of bets on that being true anyway.)</i><p>Go does not suffer from either of these traits. For me, Go is not often a &quot;fun language&quot; to code in but it&#x27;s eminently practical and is remarkably fast to pick up for what it does express. I&#x27;ve ported a couple pieces of C# application systems to Go and they&#x27;ve worked really well. But it&#x27;s kind of a grind unwinding the higher level abstractions from C# into the more primitive Go space.<p>I wish there was some way to bury Rust&#x27;s borrow checker for those parts of an application where you don&#x27;t want to care about it and then surface it gradually when you do want it. Because the elegance of the rest of the language is what pulls me back every few months.