1. 11
  1.  

  2. 5

    The flaming in HN on this topic becomes wearisome.

    I like go and code in it. What’s wrong with that and also wanting some of these improvements? Must I hate go to want the improvements or love go to not want them?

    I thought the article’s summary was great:

    Make it works -> Make it beautiful -> Make it reusable.

    Now that the first step is done. What’s next? Don’t get me wrong, go is a perspective language: channels and goroutines are way much better than i.e. pthread, but should we really stop here?

    1. 1

      In my experience, the most difficult thing is knowing when to stop. The beauty of Go is in the simplicity of the language. In contrast, C++ apparently now wants to be Lisp?