Re:Go as an alternative to Node.js for Very Fast Servers
by kibwen on Friday February 22, 2013 @01:38PM
(#5265794)
I'm groping blindly here, but from the references in that message to cgo I think it might have to do with calling into foreign code. Presumably Go's scheduler can't yield when you're inside C code (I'm not aware of any lightweight thread system that can achieve this) so you have to block there, which means you can no longer schedule other goroutines on that thread, and thus you have to spawn a new thread if you want to get any work done. But I'm just guessing here.
[ Parent
| on HN ]
There are no comments on this comment yet.