There are multiple optimizations that may be done in go as well to make it even more performant. To me, the point of the article is not to crown one language superior, so "fairness" really is beside the point, but I might be wrong.
All it says is that if you want to do CPU-bound work and split the workload across multiple threads/cores, then go will definitely be the better choice as you get really powerful concurrency primitives provided out of the box.
There are multiple optimizations that may be done in go as well to make it even more performant. To me, the point of the article is not to crown one language superior, so "fairness" really is beside the point, but I might be wrong.
All it says is that if you want to do CPU-bound work and split the workload across multiple threads/cores, then go will definitely be the better choice as you get really powerful concurrency primitives provided out of the box.
Exactly!
I think would have been interesting to see also how node handles loads if using multiple cores too as who knows it might be even more performant.