Every time a crazy workaround for node.js's shortcomings arises I think about how hardware engineers must feel. Your magnum opus is giving people 2, 4, even 16 core supercomputers and then the software engineers come along and start using this hot new single threaded tech called node. Sure, run multiple processes and then you get to spend most of the cycles passing stuff around. I think if I was a hardware engineer I'd want to quit and become a potato farmer.
Nobody is stopping you from running multiple node workers on the same machine. Singlethreadedness actually makes things easier, and even with my limited experience in Dotnet I have already had issues with thread-safety...
Comments
Interesting you can make money from this sort of thing.
Every time a crazy workaround for node.js's shortcomings arises I think about how hardware engineers must feel. Your magnum opus is giving people 2, 4, even 16 core supercomputers and then the software engineers come along and start using this hot new single threaded tech called node. Sure, run multiple processes and then you get to spend most of the cycles passing stuff around. I think if I was a hardware engineer I'd want to quit and become a potato farmer.
Nobody is stopping you from running multiple node workers on the same machine. Singlethreadedness actually makes things easier, and even with my limited experience in Dotnet I have already had issues with thread-safety...
How do you know they're making money?