To preface I would like to keep this a discussion and not a trolling thread.
Meteor is going through some changes and a lot of people don’t care for it. While listening to the latest Transmission episode with @sashko and @pauldowman I was wondering why MDG doesn’t cut off a new version 2.0 at some point in the future? Having a 2.0 could eliminate the backwards compatibility struggle.
Ruby on Rails is on 5.0 and every major release has breaking changes that can’t be easily upgraded and large companies are still on v 2/3/4 and still productive.
Meteor 1.X could be classic Meteor and the atmosphere ecosystem can exist for those packages. Security updates can still be applied and users who are happy with this stack can enjoy a stable system. Open source could add in new features as needed (but stability seems to be a major concern).
Meteor 2.0 uses a more “modern” stack and doubles down on making that as fast, easy and efficient as possible. NPM could be the only way to get packages. If React and GraphQL is going to be the ideal standard, Meteor could become something as good or better than the Ember CLI… making it the most productive Meteor stack (just spitballing).
Does this seem like this would be the most helpful for both parties?