> In your previous post. Then you list out MEAN(Mongo, Express, Angular, Node), which is all glueing. First of all, I only claimed you have plenty of glueing i

> In your previous post. Then you list out MEAN(Mongo, Express, Angular, Node), which is all glueing. First of all, I only claimed you have plenty of glueing in Rails (although you glue when working with anything, it's the degree at which I think is important). Secondly, I was agreeing with about there being options, I didn't really reply to the "why Meteor", I think I went over that enough. > I have used this stack extensively, and I must say its not even close to Rails. In fact it's not even on the same planet. They are both used to build web applications, I think they have many similarities. But yes, they do have a wide range of strength and weaknesses. > After all you guys finish your piddly todo lists, start trying to write some real business logic in Node, and see how far it gets you. There is a reason the Meteor team chose fibers. You can async.waterfall all you want but structuring your code in a synchronous manner, lets you get stuff done. I don't find it exceedingly difficult to be productive in Rails, Meteor, or MEAN. Again, each has their strength and weaknesses. And in terms of structuring code: async or not, you have plenty of options to properly organize it (eg: Deps.autorun, promises, npm's async). > People tout Node and Meteor for real time stuff. I think because it tools itself well there. > I could do similar things with SSE and Rails/Ember or Angular. Right, no one is taking Rails away from you. > The users of your applications don't care if you use Websockets True, most users won't care about the specific technologies used to load a page. But it could play a role in the experience, which is something they will care about. > and really most of the time you don't even need Websockets, you just need SSE or long polling. See, here's the thing "most of the time", but not all of the time. So there are cases for each. Long polling has plenty of cons, and SSEs don't provide you with a bidirectional channel. That's important for some applications.