The articles clarifies why he managed to get better time.
Hint parallelisation.
Discussion
yes, i know about this, i wrote a miner for my own custom proof of work on a shitcoin upgrade chain and when i ran it as goroutines (these are not strictly parallelised) it was 20% slower than when i set up child processes to mine on a single kernel thread
20% was the difference, this is back in 2019, i'm sure that Go's coroutine scheduler is better than this now but i doubt it is as good as kernel threads
this is something you can do well with any language that has decent optimization and (heavy) kernel threads that do bulk work
coroutines give you low latency, not high throughput
Right, I never claimed the language was the main reason, I just told you what he did.
If you would just read the article you will see it was a huge improvement.
Not sure what exactly you are mad about though.