3 ms·
I think that much of the reaction in the original post comes from the overly-bombastic headline: "Why meteor will kill Ruby on Rails". If it was sold as "Meteo
by nostrademons 13y ago
I think that much of the reaction in the original post comes from the overly-bombastic headline: "Why meteor will kill Ruby on Rails". If it was sold as "Meteor.js: an exciting new technology for building real-time webapps", I could get behind that, because building real-time websites is currently hard and Meteor makes it easy (easier?). But if you say Meteor is going to kill Rails, you are positioning Rails as Meteor's competition: and when I look at what Rails is used for (quickly building multi-page DB-backed sites with relatively small levels of interactivity), Meteor sucks at that job. There's little reason to use it, and a lot of reason not to.
Hype and blind optimism kills promising new technologies far more often than competitors do. Picking your competitors carefully is important. If you position Meteor against Backbone or Angular, you might have a case, and then we could evaluate based on the technical merits. But if you position it against Rails, they're built for completely different use-cases, and so of course Meteor is going to fall down.