Why I Don't Like Golang (2016)
Does anyone remember reading K&R for the first time?To me seemed like C was such a tight, perfect little design.Only thirty keywords, and simple consistent semantics.¹When I first learned it, it was still pre ANSI, and you declared a function like thisint f(a)char *a{}The ANSI style function declaration was maybe the only innovation that came after that that significantly improved the language.I remember in the late '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.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.The K&R book is worth a read if anyone missed it.  It's beautifully written.  A far cry from the 'opinionated' copy that you often find on the Go website.Personally, I don't think you can make similar claims about Go's design or the 'because I told you so' tone that surrounds it.1: Yes, I know, undefined behaviour, but this is my post and this is how I feel about C.