Huh, impressive for Erlang, beating a newer, statically compiled language, while being interpreted and with dynamic types.
Huh, impressive for Erlang, beating a newer, statically compiled language, while being interpreted and with dynamic types.
[1] http://jlouisramblings.blogspot.com/2013/01/how-erlang-does-...
Yes, Erlang has admittedly had decades to improve the scheduler (versus a couple of years for the gc compiler in Go), so this is quite literally true.
However, you should know that goroutines are pre-emptively scheduled now; the "scare quotes in your comment seem to imply that they aren't: http://golang.org/doc/go1.2#preemption
In practice that means that if you call a function somewhere in your infinite loop, you'll get preempted. It's still possible for a single goroutine to steal an os thread.
Practically speaking though, I feel like nobody should be scared away from go due to it's lack of full pre-emption. Seriously, don't write an infinite loop with no function calls.
versus an interpreter that got decades to mature (and HiPE to speed things up some more)