Ok, as someone who has been actually building apps on Node for about 1 year AND working with a largish Scala codebase for the last six months: > Not to mention

Ok, as someone who has been actually building apps on Node for about 1 year AND working with a largish Scala codebase for the last six months: > Not to mention the fact that its balls-ass slower than some straight un-optimized Scala. I don't see the point of comparison here. Slower/faster is meaningless without the context. Apples to Oranges. And, Scala has it's own issues. Yeah, the JVM's performance is there, but bringing your team onto a Scala codebase is not easy either. > It provides the least amount of aid and comfort to the programmer and its nigh-on-impossible to follow the code 6 months later. Anyone who has developed more than a Hello World in Node will know that the problem of callback sphaghetti can be circumvented using events, promises and async libraries. Yes, until the language itself offers an async construct, this will be an issue, but frankly there are ways to get around it. > JavaScript has very little support for any of those nice things: it doesn't even have namespaces, for chrissakes. Client side JS has no module system. But Node.js has. At this point, I really wonder if the OP has actually worked at all with Node. > It seems to me that people who are really crazy about Node.js are people who only knew JavaScript to begin with and to whom none of the above would ever even occur. Another baseless claim. I urge you to go see the GitHub profiles of Node core committers. Seriously.