With PHP and PostgreSQL we could scale up, but it felt really hard and gave us many sleepless nights. Using Node.js with a MongoDB backend scaling up is quick and easy; but because Node can handle more traffic, you don’t need to as quickly.
It's interesting to read an experience where Node's performance largely pays off when building traditional sites. I've often read that Node's performance really only pays off when building realtime apps. Maybe I misinterpreted, perhaps it was meant more as the large set of features provided by frameworks like Rails/Django transcend Node's performance boost?
We pivoted from being a Drupal shop to being a Node.js shop just over a year ago. I don't think a single one of us has regretted that decision.
Come on, let's stop the Node.js ridiculous hype already.
1. It's JavaScript! JavaScript is a terrible language. The fact that you need to read "JavaScript: The GOod Parts" in order to use the damn thing is an indicator of that.
I don't care that it's supposedly "lispy."
2. Code re-use at every level
Does any project actually do this? Is there any sort of front-end library that actually works both in Node and in the browser? It seems like more of a pipe dream to me. An awesome idea, for sure, but never actually implemented in practice.
3. Strong, responsive and enthusiastic community
This is moot if there aren't good libraries available. There are, but other platforms have far better ones available and I wouldn't count this as a plus for Node.
Maybe you're talking about Reddit or HN headlines, though.
4. Large productivity gains in HTML & CSS using Jade & Stylus
Never used them, but finding a library or framework that works for you is awesome.
5. Wealth of hosting options: No.de, Joyent’s SmartMachine, Heroku, Nodejitsu
You can say the same thing about PHP too. That doesn't make it a good reason to use it.
6. Make your developers famous
Seriously?
7. Developer happiness
HN fame?