Half a million lines of Go
I&#x27;ve written a bit of code in Go, and the problem I have with it is primarily it feels really outdated for a &quot;modern&quot; language - every time I use it I feel like I&#x27;m dealing with something written by someone who really hated Java in 2005.  There are features that could be added to the language that would make it more readable and less error-prone without compromising the simplicity of the core language. Generics are the famous example, but the one that really gets me is the the lack of nullable type signatures. This is a great way to avoid an entire class of bugs that nearly every modern language I&#x27;ve used has evolved a solution for except Go.<p>Another issue I have is the reliance on reflection. In general, I think if you have to rely on reflection to do something, that usually means you&#x27;re working around some inherent limitation in the normal language - and the resulting code is often far less readable than the code would be in a more expressive language. Lots of Go libraries and frameworks are forced to use it in a lot of cases because there&#x27;s just no other way to express some really basic things without it.<p>I really want to like Go. There&#x27;s a lot I like - the &quot;only one way to do something&quot; approach means that code always feels consistent. Errors as values is a far superior approach to exceptions. I had to write some for a job interview project a while back and it felt really refreshing, but every time I try to use it for a personal project, I don&#x27;t feel like I&#x27;m getting anything out of it that I couldn&#x27;t get out of say, Rust, or modern, typed Python.