> Finally, at the end of the day, if a JS framework becomes a better solution than anything else I use, I will certainly switch.<p>I'd recommend Matt just to dive deeper into Node, Express, Flatiron and all the 8,000 packages and he will discover tons of better solutions instead of sticking to the current status quo. And Node often feels faster, easier and less cumbersome than Ruby/Rails (once getting used to callbacks). I didn't mention performance which would be one reason to use Node—Matt wrote he would use it because being the new cool framework.<p>Ruby mainly exits because of Rails. Rails is the most automated web framework on earth, it's great and paved the way. We use both every day as first choice because of its maturity, the community, the high day rates we get, ten thousands of great gems seaming-less working together, the convention everybody knows.<p>Definitely Rails is the best full-blown solution for web development but real innovation happens somewhere else.<p>EDIT: disagree != downvote, reply if you disagree