Although such questions are rightfully warranted - you are investing in it after all - the answers, I believe, are simply in favor of Meteor and MDG’s vision.
Evolution and innovtion are inevitable and in a such high velocity realm like software development, it should even be considered absolutely necessary.
MDG does one better and goes to great lengths to be backwards compatible, while proposing carefully crafted upgrade/migration paths. Had it not been the case, most Meteor apps from 6 months ago would be breaking today. But I do find that my apps from 3-4 years ago still run just fine, albeit not exactly easily updatable due to third party dependencies lacking support. But I’ve had good mileage with all of them, in fact last week, while needing to demo a very old app, realizing it had been pre 1.0 and needed upgrade, it took me about 10 minutes to upgrade to 1.3.5, granted it was a rather small app with very minimal 3rd party dependencies.
Regarding deprecations of technologies, well that’s eventually going to happen. Mind you they still do support them, and they even agree to hand over governance to the community for those would be deprecated parts. But you should also understand that if they are deprecating something and advising the community to move on to some X stack, you probably should listen. I used to be a vocal member of the “we want blaze” camp until I decided to take an actual, willing and positive look at their suggestion, React and now it is my go to ui stack and I’m actually trying to see if it would be worth converting old Blaze apps to tap into what React has to offer for the future!
And it is all the same with GraphQL. I keep finding myself trying to tame reactivity, tearing down subscriptions to convert them to method calls or trying to mark them as non reactive, only to see that where I’m trying to architecturally head towards, MDG is already there with Apollo! There is a reason some very smart people decided to bet 20 million dollars on them some years ago when they did not even have any monetization strategy whatsoever! They’re even on the innovators quadrant of a Gartner report. For those who are not familiar with what Gartner is and what it means to be on one of their reports, let alone the magic quadrant, that’s h-u-g-e!
Anyhow, regarding their vision, I think they are spot on with their strategy on separating their core offering into
- Data (Apollo)
- Build Tool (Meteor)
Now, Apollo is arguably the most innovative GraphQL solution out there.
On the other hand, trying to achieve the same using a host of build tools, getting them to play nice with each other, configuring endless files, digging up gotchas in documents and github issues would probably take at least a week or even more, for what, to be able to say “Hello World”.
I don’t know what MDG’s plans and intentions are in monetizing their innovations, but they are smart people and their investors must as well be as smart, given their track record on other investments they’ve made. If those investors have cast their vote of confidence on MDG, why should you care if Galaxy makes money or MDG may or may not be able to profit? How much revenue did Instagram generate before getting acquired for a sizeable $1B? 0! Z E R O that is, 0!
I think what we can do to pay back is to actually enjoy what we have and stop second guessing this every other day. Yes they do have notoriously bad communication skills, but hey, I’d rather have them giving me the next feature then explaining me why and why not!
So there you go, I believe you should grab tight on MDG’s vision, probably even be an early adopter as much as you can, and sleep sound knowing you’re in good company!
Oh and, where else did you ever see such a vibrant, selfless, helpful community? The worst case scenario, you will have made a lot of very smart friends here on the forums and should MDG ever tank - god forbid - you’ll have them caringly embrace and guide you towards a solution