I agree but I don't think event-based approach is poor as you're stating. Twisted or EventMachine use that approach and are pretty well known for that. It looks like it works wonderfully well in a couple of particular cases but Node as every new language got its couple of pioneers running to create the new "Rails/Django" in that language asap. This is in my humble opinion the issue there.
Another issue is that Node is actually using Javascript, meaning it get a broader community than any new general language. But this community isn't by definition well familiarized with threading or async situations. These developers can easily slide into the "silver bullet thing".
Explaining the core notions behind event-based solutions and threading ones to a "nodejs hipster" usually allow him to understand the right uses cases for it, at least from my experience.
Another issue is that Node is actually using Javascript, meaning it get a broader community than any new general language. But this community isn't by definition well familiarized with threading or async situations. These developers can easily slide into the "silver bullet thing".
Explaining the core notions behind event-based solutions and threading ones to a "nodejs hipster" usually allow him to understand the right uses cases for it, at least from my experience.