1. 10

  2. 5

    This is not a useful article.

    1. 1

      To be honest, this doesn’t seem good to me, nor bad. Most people get into something in which they can simply learn and use it. Briefly, they switch from Python or Node.js to Go because they are familiar with the syntax (Go solves some problems, though).

      1. 4

        Actually, the reason I didn’t switch to Go immediately were all the syntax gotchas (you think it would be written in a way and instead it’s some other way). I personally switched to Go both because of the performance and memory usage improvement (going from over 40MB for a simple node web app to just 3MB) and because managing microthreads with channels is just way more intuitive than using async.

        1. 2

          It sounds like you are not kinda those people. I personally just don’t like Go, because of the paradigm, lack of things I’m interested in, etc. The only reason that might interest me to give Go a shot is performance. But in most situations I need to get things done in parallel right, in which I found Erlang a good fit. However, I won’t use Go if I need performance. In fact, for me, there’s no reason that could motivate me to use Go in production.