Systems Languages: An Experience Report
I think everyone agrees that &quot;fighting&quot; the borrow checker is annoying, however at the risk of sounding like a Rust apologist I find that a couple interesting things have happened over ~2 years with the language:<p>1. The borrow checker usually kicks in when I want to take shortcuts that would bite me in the future. 90% of issues I hit with it can be solved with copy&#x2F;clone.<p>2. When I take the time to satisfy the borrow checker I find my <i>architecture</i> is better. Usually I&#x27;m tripping the borrow checker because I don&#x27;t have a clear single-owner or separation of concerns.<p>Also, if you&#x27;re looking for an &quot;easy&quot; to program languages there&#x27;s tons of them out there and it definitely doesn&#x27;t make sense in my mind to use Rust where C#&#x2F;Erlang&#x2F;Java&#x2F;etc fit the domain space better.