3 ms·
To be fair, his argument against Node.js is applicable to any system with co-operative scheduling (twisted, tornado, eventmachine, Go etc), and the only way aro
by findjashua 12y ago
To be fair, his argument against Node.js is applicable to any system with co-operative scheduling (twisted, tornado, eventmachine, Go etc), and the only way around it is pre-emptive scheduling (Erlang/Elixir, Haskell etc). Node has a lot of problems, but co-operative scheduling is not one of the more important ones.