Go 1.18
This is very exciting! Generics will be helpful for some, I&#x27;m sure, but my reading of the winds is that people will find other idiosyncracies of Go to latch onto and complain about. It seems to me the next object of hatred is the lack of sum types.<p>I would like to understand a bit more about where a lot of the Go criticism comes from. Of course some amount of it comes from direct frustrations people have with the language design, but I suspect that doesn&#x27;t account for all of it. It seems to me that the intensity with which some people fixated on the absence of generics cannot be explained just by frustration with writing non-generic code, which by all accounts was annoying but not overwhelmingly so.<p>So, for those of you who are willing to explore the part of this that goes beyond a simple rational analysis and criticism of language design, whats bugging you?<p>Sometimes I think the core irritation with Go is its simplicity. The suggestion that easy to learn languages can be effective too is somewhat humiliating, as we get attached to the pride of mastering more complex languages, and the suggestion is that some of the struggling we went through was unnecessary, and that folks who wont struggle as much might be able to be effective too, in fact the suggestion is that maybe our pride was misplaced.<p>Theres also a suggestion, in the fact that Go has opinions, that other opinions might be &quot;wrong&quot;. I think this may bug people, who would take up those other opinions or see merit in them, a lot. There&#x27;s also a bit of an anti-expertise &quot;who are you, Go creators, to say you know better than me how to design this program&#x2F;engage in software development?&quot;<p>In any case, it&#x27;s something I&#x27;ve been trying to figure out for a while and I don&#x27;t think I have a complete explanation still. Curious to see what others think.