Rust vs. Go
I&#x27;m not quite willing to dismiss Rust merely for being hard to learn, but after poking around in both Go and Rust for a few weeks, I feel like I could build a project in Go (slowly, and with a lot of googling), but I don&#x27;t feel like I could build anything in Rust without a <i>lot</i> more learning.<p>Rust has the same problem as C++ (to a lesser degree; maybe it&#x27;d be more fair to compare it to Java), in that if you&#x27;re a casual coder who dips into a bunch of different projects in a bunch of different languages without ever really specializing, it can be overwhelming. Go is much more readily accessible; partly because it is less ambitious, and partly due to philosophical differences. I can read most Go code, today, having only worked through &quot;A Tour of Go&quot; on the website; I can&#x27;t even begin to read Rust code after similar time&#x2F;effort invested.<p>So, yeah, Rust really <i>is</i> hard. It may be necessary complexity to solve the problems they wish to solve. But, it means I&#x27;m unlikely to ever have the time to invest to make it a part of my toolbox, unless it becomes my primary job; whereas I&#x27;m already almost there with Go. I&#x27;ll probably build something real in Go within the next month or two. It can be something I do for fun, in my spare time, and I can expect to get useful results.<p>I want to like Rust. I&#x27;m just finding it hard to get to know Rust.