Good point, and I&#x27;ve seen this stuff referenced before, so perhaps my comment above is a little over-stated.<p>But my confusion remains: how big are all these Node apps, what are they being used for, how robust have they proven to be, how happy are these companies with their Node server side code, how far will these Node apps be extended, how much more Node will these companies be implementing, etc.<p>My skepticism  is fueled, in part, by numerous incidents like the one recently on the Atlanta JavaScript Slack channel, where a Node Evangelist was telling everyone how WordPress had rebuilt their infrastructure in Node. Problem is, WordPress has done nothing of the sort. They actually built a small downloadable app for WordPress admins to use in managing their WordPress sites, as far as I could figure out. Which is precisely what Node MIGHT be considered good for, no doubt about it.<p>But that&#x27;s not what our Node Evangelist friend was preaching. And I just get the feeling that a lot of people who are spreading the Node Word are misunderstanding some of the facts on the ground. There might be some wishful thinking in Node Land. Because I wouldn&#x27;t choose Node over any of 6 other server side languages right now, and I sure wouldn&#x27;t attempt to build robust apps for our clients on such a fragmented and messy ecosystem of modules and shiny fads.<p>On that note,, where&#x27;s the Django or Rails or .NET or Spring of Node Land? I can&#x27;t seem to find it, and without it, Node is a non-starter for so many professionals. Just seems obvious, but maybe I&#x27;m wrong.