2 ms·
I'm personally ignorant of Go because I haven't used it yet, but Node being single threaded isn't as big a deal breaker as you'd imagine. If you use it like oth
by malandrew 14y ago
I'm personally ignorant of Go because I haven't used it yet, but Node being single threaded isn't as big a deal breaker as you'd imagine. If you use it like other environments, you'll code yourself into a corner, but if you instead rely on forking and interprocess communication on the same machine or communication between node processes on separate servers, you end up with an acceptable concurrency model. The single threaded nature of Node generally promotes horizontally scalable designs.
I want to try Go myself, but node isn't as awful as you think.