Two points for you: 1) CoffeeScript does not require Node...npm may make it much easier to install, but you can definitely run it without installing Node. We ru

Two points for you: 1) CoffeeScript does not require Node...npm may make it much easier to install, but you can definitely run it without installing Node. We run the compiler as a Maven plugin, but it's distributed as JavaScript and all you need is an interpreter. 2) There are templating languages that have interfaces in both JavaScript and other languages to allow the same templates to render on both the client and the server. We use Java on the server, so we're looking at Closure Templates, but for Python, you might want to look at Mustache. If you've already finished your project, I'm not going to try to convince you to move away from Node, but if you've got a lot to do still, you might consider sticking with Python. I'm not saying that Node isn't a workable solution on the server side, I just don't think it's proven that it is the way that Python and other, more mature platforms have. I don't give too much credence to inflammatory posts like the one being discussed, but when I see posts like: http://news.ycombinator.com/item?id=2519674 http://news.ycombinator.com/item?id=2519674 from a developer I respect, it gives me pause. That post is 18 months old now, so the situation could have changed. There's something to be said for building things you know are rock solid and won't result in 2am notifications. That's my perspective, so I try to stay away from the bleeding edge. For stuff that's not critical, I'm more ok with taking a few risks. But someone's got to be the one that takes those risks in a mission-critical environment to figure out which of the new technologies will become proven and which will fail, so I disagree that these people are doing life wrong. If it wasn't for people like them, my way of doing life right wouldn't work.