> NodeJS is an attempt to get cheaper backend programmers because everyone has extra front end developers lying around for projects. The problem is that most front end developers I know don't know shit about big data or working on real problems. Their biggest fear is if a button is pretty and the popup works in IE8 and the latest jQuery UI.
No, it really isn't and nobody with any experience of it believes that. It's for when performance requirements are such that you want to control your own threading rather than letting the operating system do it for you. It's more like programming in assembly than in a high level language and as such requires a much higher level of knowledge on behalf of the server side programmers than something relatively straightforward like java let alone python or php.
Just for the record, I was a c++ programmer for 15 years an EJB (curse its fucking name) programmer for 6 years, and have been doing a lot of front end javascript stuff for 6 years plus some node.js for the last 2 years. I just delivered the server end of a project which deals with more data than youtube ( http://www.manything.com/ ). Get off your fucking high horse about front end web development. Big data is a fucking walk in the park compared to delivering a decent user experience on web platforms.
I'm not here to praise node.js: many environments have pitfalls, but node.js greases the sides, put stakes at the bottom and threw down a bunch of venomous snakes just to be on the safe side. Plus, you're working in a language where
[1, 2] + [3,4] === '1,23,4'
However, having said all that, it has its place, its just not where you think it is.