Why I went from Python to Go (and not node.js)
Another gonatic?  I'm immediately reminded of the days when everyone who liked D proclaimed it would overtake C++ and rule the world with terrible, contrived examples: "let me show you why my language is better than yours by completely misunderstanding how to solve a problem, then implementing that broken/overengineered solution in your language, then compare it to something my language's API can do for me, just so we can see how much simpler that bad solution is in my language!"<p>The insight to async I/O is that this server, for this I/O bound task, will perform as well as your GOMAXPROCS example:<p><pre><code>    require('http').createServer(function(req, res) {
        res.writeHead(200);
        res.end("hello world\n");
    }).listen(8000);
</code></pre>
But it's a lot simpler.  You don't need to bolt on parallelism when you don't actually need parallelism.  There are valid reasons to use Go, and there are valid complaints against Node.  I don't see any of either here.