Why I Don't Like Golang (2016)
Does anyone remember reading K&amp;R for the first time?<p>To me seemed like C was such a tight, perfect little design.<p>Only thirty keywords, and simple consistent semantics.¹<p>When I first learned it, it was still pre ANSI, and you declared a function like this<p>int f(a)<p>char *a<p>{<p>}<p>The ANSI style function declaration was maybe the only innovation that came after that that significantly improved the language.<p>I remember in the late &#x27;80s knowing my compiler so well that I could tell you what the stack frame would look like pretty much anywhere in my code.  It was awesome to have that level of familiarity.<p>Soon after that things started to get more complicated, and I did a lot of Java, and I never again felt as dialed in to those languages as the late 80s C that I started out with.<p>The K&amp;R book is worth a read if anyone missed it.  It&#x27;s beautifully written.  A far cry from the &#x27;opinionated&#x27; copy that you often find on the Go website.<p>Personally, I don&#x27;t think you can make similar claims about Go&#x27;s design or the &#x27;because I told you so&#x27; tone that surrounds it.<p>1: Yes, I know, undefined behaviour, but this is my post and this is how I feel about C.