Less is exponentially more (2012)
A few years ago I started to play with go.  First impression was great.  But a month or so in I started to having more and more doubts.  As a Java&#x2F;C++ programmer I was missing especially the generic collections. Slice and map are a good start, but not enough.<p>Then one day I had to implement the swap operation for sorting. Again.  And I thought that even C&#x27;s qsort was better, and WTF am I wasting my time on this half-assed language.  I dumped it, tried rust, and even with its slow compile times I couldn&#x27;t be happier.<p>Now a few releases later, they fixed sort so I can only implement compare.  Sorry, it&#x27;s not nearly enough.  Essential parts are simply  missing. Exhibit A is source code generation, a clear indication go isn&#x27;t enough on its own.  I&#x27;m not working with an ecosystem where my human time is less important than the language philosophy.  I want to express a repetitive pattern in the language, and then never think about dumb bureaucratics again.<p>It was a near miss, though.  SOme things are clearly correct.  I want to look again when they finally have generics, and some basic collections.  I hope that day comes and I can give it a new chance.  But until then, less was simply not enough .