News for hackers. Stuff that matters.
Re:The State of Meteor Part 1: What Went Wrong by yawboakye on Wednesday January 20, 2016 @11:57AM (#10939438)
Rails didn't hit that wall. Neither will Ember. FYI Ember is introducing new ideas by the second (pods, composable components, components over controllers, DDAU, etc) but the community eagerly awaits and embraces them. I don't know why that is.
Re:The State of Meteor Part 1: What Went Wrong by muloka on Wednesday January 20, 2016 @02:17PM (#10940569)
Rails forked sometime ago (around 2.0) into Merb then later on merged back into Rails 3.

Similarly Node forked into io.js then later back into Node 4.

Re:The State of Meteor Part 1: What Went Wrong by flippyhead on Thursday January 21, 2016 @06:32AM (#10944576)
This is really a fantastic point. It's sometimes as if people think these type of projects exist in isolation and any perceived flaws are permanent. They often fail to appreciate how much the flaws will invoke a response to address them, making them better than they would have been had the flaws never been strongly felt by the community in the first place.