Skip to content

Comment on IBM article explaining why Tomcat and Apache are better then Node.jsparent

Comments

"Currently, Node doesn't provide a default way to create dynamic pages."

I don't see one either, am I missing something? http://nodejs.org/docs/v0.4.7/api/ (I do see one mentioned in "Recommended third-party modules" but that's not "default" or to use probably a better term, batteries-included.)

Node does not seem to be generally pitched as a framework to push out more templated page-oriented PHP-style web pages. Isn't this supposed to be most of the point of Node.js that it's meant for other use cases that are poorly-served by the page-oriented servers and frameworks?

And for that last one, while it is true Node wouldn't be my first choice I have seen sites based on Apache where I could see using Node.js to server images and do something else Node-y. Some common configurations of Apache can be really freaking heavyweight per-request before it even necessarily gets to your code, and using a separate server to serve up static assets is common. True, Node wouldn't be my first choice but I'm not sure it's necessarily a terrible choice.

The first one is true; like I said, it does have errors, and is generally poorly-written. But I think a lot of it is that he's writing from a perspective that you don't share, but not necessarily a wrong perspective.

what is the default way to create dynamic pages? must have missed that!

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.