The author came to this Ruby on Rails dichotomy for the very same reason other frameworks/languages are doing so: 1) To cash in on Rails's good rep and outstan

The author came to this Ruby on Rails dichotomy for the very same reason other frameworks/languages are doing so: 1) To cash in on Rails's good rep and outstanding efforts in the field in the past 10 years or so. 2) Because the author knows that people are fiddle and that new fashions are made and destroyed every other day, so why not scare people a little if that can help Meteor get off the ground, eh? 3) Because shitting on Rails is trendy these days and it's always very easy to precisely target the relative weaknesses of a framework whilst pretending to ignore its strengths. Anybody with half a brain can play that game. That being said, it doesn't diminish Meteor's merits in any way and I really hope its community thrives and grows in the next few years. The first few years are always the best ones :)