Twelve Years of Go
I can attest to the fact that programming in Go taught me a lot of good engineering. I certainly find myself better trained at handling errors, for example.<p>However, I always feel exhausted when implementing real-world systems with Go given the lack of $things (that everyone feels is a virtue). Over time I realized that a lot of people just aren&#x27;t as lazy (or scared of breaking things) as I am - they find it easier to copy code dozens of times and then fixing them all in one go using their ninja refactoring skills. Just a different kind of tradeoff, at the end.<p>So given how laborious it is to make anything more than simple programs (because of the amount of copy-paste-driven-development required), I generally avoid Go unless I&#x27;m writing a webservice.<p>For me Go&#x27;s virtues are static typing and wide variety of community packages to do things. The whole &quot;oh not having features is a feature&quot; thing is just an opinion for the sake of having an opinion. otoh, I damn excited to have generics support soon finally :)