Rust vs. Go in 2023
I don&#x27;t get paid to write code in these languages; my enthusiasm in exploring them is limited by the amount of energy I have over the weekend. Honestly, I don&#x27;t see Rust as anything but a code-rewrite language.<p>I find Rust to be unintuitive, and I don&#x27;t think it is a language designed to be a &quot;problem solver.<p>So, what do I mean by a problem solver? If you have a problem and you write code by exploring different solutions, continuously improve, and write hacky stuff where the goal is to simply solve a problem.<p>Rust is not a problem solver; it is going to fight you all the way through because of its emphasis on programmatic correctness. With Rust, you have to have the solution first, consider the language-specific caveats, and write something in such a way that you don&#x27;t go back and have to improve it. I suppose that is how programming is supposed to be done - in a clear and structured manner. But let&#x27;s admit it, nobody does that.<p>On the other hand, Go is a language that sits between Python and Rust. Python is THE problem solver language, and Rust is an elegant and good etiquette language. Go just works as a hackable language with the benefits of a compiled language and type support.<p>My plan with Rust vs Go for the time being:<p>- If I need to solve a problem and can do continuous improvement on the codebase → Go
- If I have the problem solved, I have the resources to do a rewrite → Rust