3 ms·
I'm really pretty anti-node, but this article isn't very good. The concerns here are mixed up and not very thorough. All these points need graphs, charts, somet
by andrewvc 15y ago
I'm really pretty anti-node, but this article isn't very good. The concerns here are mixed up and not very thorough. All these points need graphs, charts, something solid to anchor them to. This is the sort of article that polarizes, but doesn't add to the discussion.
It starts off strong talking about a high bug count, but never gets into specifics there.
As far as scaling across cores goes, it's disingenuous to suggest that node can't do this, there are a number of options here. Message passing, for instance, does indeed work.
As far as nested callbacks sucking, I totally agree. But a walk through why would add a lot more substance here as well.
- nephics 15y agoUnfortunately, this way of stating unqualified arguments as basis for reasoning is quite prevalent on the Internet. Keeping it to node.js bashing, this guy takes the discussion to a slightly lower level: http://youtube.com/watch?v=1e1zzna-dNw http://youtube.com/watch?v=1e1zzna-dNw
- highace 15y agoHa, I liked that. But slagging aside, are the points he makes baseless?
- AdrianRossouw 15y agoHow is that lower level ? He tries to discredit node by taking apart the copy on the front page of nodejs.org. It's all conjecture and ad hominem.
- mnutt 15y agoI don't think it even starts off strong with the bug counts. That wasn't node, but using Chrome/v8 directly to parse web pages for their web crawler. I'm not the least bit surprised that parsing unfiltered HTML from the internet dominates their bug count. I also won't be surprised if their rewritten scala HTML parser also dominates the bug counts.