3 ms·
The whole point of Node is evented I/O in JavaScript. That's it - it doesn't take a stance on frameworks. The point of npm is ... to be a package manager. Exp
by nilliams 14y ago
The whole point of Node is evented I/O in JavaScript. That's it - it doesn't take a stance on frameworks.
The point of npm is ... to be a package manager.
Express is a framework. I admittedly don't know much about it, but I believe it basically has pluggable middleware, like Rails.
Not sure these things share the "point" you are claiming they do.
It's great Node has both framework choices and a wealth of small modules that do one thing. I think there's room for both.
- nilliams 14y agoThere was a bit of snark in this comment with the "..." which I apologise for, but I think my point was fair. Trying to paint Node as an anti-framework ecosystem is disingenuous and this is clearly not a goal of either Node, npm or Express. I love Node, and am consistently impressed by npm, but pretending that these technologies represent a "paradigm shift" and some sort of cohesive shift away from frameworks is faintly ridiculous. If you work on a team and are faced with the task of creating a large app your choice is to pick a framework or create your own from libraries. I'd argue that a (good) framework is likely to be better because the conventions are likely clearer and better documented than anything you cook up yourself by combining libraries and filling in gaps with your own code.