4 ms·
Throwing out the Windows 3.1 argument is an effort to throw mud at the wall and hoping it sticks. Node is meant for network programming, where letting the OS s
by baudehlo 11y ago
Throwing out the Windows 3.1 argument is an effort to throw mud at the wall and hoping it sticks.
Node is meant for network programming, where letting the OS schedule which process can operate on the network data is the right thing to do. There are certainly problems with the lack of ability to lightweight share data between threads/processes/coroutines but for the most part it works very well.
There are things node shouldn't be used for due to that. So use another product.
- amelius 11y agoIt works well for servers which merely move data from A to B. For servers that actually do some useful computations, the programming model simply does not fit. In modern web applications, latency is very important, and that is the very thing you are sacrificing by choosing the cooperative multitasking model for your server.
- baudehlo 11y agoIsn't that basically what I said?