I feel that I need to do a lengthy one here. I’m sorry…
That’s an overly negative impression which comes from the mindset that Open Source projects should always be committing or they’re abandoned.
Meteor is being under development for 6 years now, it’s unrealistic to expect a commit/feature rate of the project to be similar to that under heavy construction. By your definition I’d say 90% of open source projects are just abandoned. It’s like looking at a building which is almost complete, and comparing it to a hole in the ground and saying look construction rate is not the same, that’s just absurd.
The biggest mistake developers and businesses make is to look at projects like this and mark it as “done”. These are projects that need continous updates, refactors, regular interactions with the community and if possible new features aswell. Ecmascript would have been swept away by now by other modern languages if it was still in its old v5 form.
I suggest you read Martin Fowlers “Refactoring” book. Its about ‘evolutionary systems’. It fits nicely on this whole topic: https://martinfowler.com/
There are 2.2k views on this thread alone since it has been posted, obviously a lot of people care. Also the “The single developer” did an incredible work in bringing the system up to date, I’ve seen many projects with 10+ devs not accomplishing similar feat due to lack of skills, poor management and/or decisions.
I totally agree with this. Meteor and some of its contributors have archieved much more then whole teams combined. Most projects also fail because of the reason you mentioned. I do feel however that its not the MDG people’s skill level. Its lack of Management, priority and Marketing that kills it atm. I totally understand their business decision though. Meteor with Galaxy is a cashcow and it will be for some time. It had its investments, but Apollo seems to be a more strategic option given its momentum.
However, Meteor is no exception. All popular frontend projects have some really bright people that could easily replace a team of 10+ devs. Evan You? Maybe Dan Abramov?
Do I agree with MDG’s decision to go full Apollo and leave the Meteor project? No! In the end it will bite MDG, because if they drop Meteor’s support, why wouldnt they do that with Apollo as soon as momentum fades when it enters the Trough of Disillusionment on the Hype Cycle?
And for the packages, there has been clear push toward using NPM packages, but the community did create Redis oplog and other crucial Meteor specific packages when needed.
You’re highlighting some of Meteor’s biggest pains here. Hence why I like this original topic. Should there be a v2? Maybe one that breaks with Meteor’s package system? What about Fibers? What about Minimongo and DDP? Would Angular 1 still be here if they didnt decide to break with its legacy stuff? Good question. Great topic to talk about with the community.
The biggest issue surrounding Meteor up to date are the FUD and the skewed negative opinions not being countered by PR.
Yes and no. Most of the things that people mention are true (harsh but true)! Meteor ‘was’ not suitable for most websites that simply required SSR and a static API. MDG ‘is’ not active on topics, pull-requests and not even social media atm.
Compare it with React, Angular, Vue, Ember, Nuxt, Next and Laravel (Laravel is I think older then Meteor and is still actively being developed, maintained and talked about). The competitors that were not even in Meteor’s water, are catching up with toolsets like Webpack that directly compete with one of Meteor’s current USPs: Hot Code Pushing and its build tool: vue-loader for example is using HMR and is really fast and easy to configure. SSR out of the box in Next and Nuxt anyone?..
MDG did so much great things. It has brought some awesome technologies on the table, but if they keep on ignoring us, it will become a dead end.