101–107 of 107 posts
Earlier quoted context omitted.
Not you though, sounds like!
Sarcasm, nice. But seriously, I'm new to Node. If I see examples of bad practice on the home page, I've no way of knowing if the framework is going to be teaching me more bad practices in the areas I'm not familiar with yet.
Earlier quoted context omitted.
Sarcasm, nice. But seriously, I'm new to Node. If I see examples of bad practice on the home page, I've no way of knowing if the framework is going to be teaching me more bad practices in the areas I'm not familiar with yet.
I really hope you start using a framework. This would free up more time for you to develop a sense of humor! :)
Earlier quoted context omitted.
Sarcasm, nice. But seriously, I'm new to Node. If I see examples of bad practice on the home page, I've no way of knowing if the framework is going to be teaching me more bad practices in the areas I'm not familiar with yet.
I really hope you start using a framework. This would free up more time for you to develop a sense of humor! :)
The whole point of Node/npm/Express (as a popular module) is its modularity. Node is not just about JS on the server, it reflects a paradigm shift -- a movement away from too much abstraction and magic back to lean and simple systems. And it's unbelievable fast. Sorry to say but such frameworks and ideas are from the last decade (Rails was the main reason why I switched to Node).
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 module…
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.
Earlier quoted context omitted.
I really enjoy using CompoundJS for quick prototypes. Wish there was a larger community though; well, really, I wish any of the MVC nodeJS frameworks had the kind of community that Rails and Django have.
I agree. It will probably take someone making successful site and the word will get out. My experience with it was that it was super fast, very responsive, so I imagine it can handle more trafic then rails I am currently using. It is no rails as rails has features that are out of this world, but you often don't need those...
Earlier quoted context omitted.
Why not?
Because GET requests can be saved as bookmarks, copied and pasted, indexed by search engines, etc.