Break things and move fast.
I think MeteorJS is moving fast, and also actively & positively embracing the ecosystem, integrating with webpack, react (native), npm & many other very great tools.
Meteor is evolving towards the right direction and in a fast pace with a community of high talents, I believe Meteor has a bright future.
Reading this thread just repeatedly reminds me of this:
I’ve been an avid reader of that webcomic since I think 2008? It’s a video game centric comic which does all sorts of one offs about things that pertain to gamers. This one was done late last year, after there seemed to be one “gate” after another in rapid succession. Since then I’ve just kept this particular strip around because it’s relevant so freaking often!
OMG Yes, so much this! Thank you for “fixing” it!
Hey @kaiyes I looked up feathers js that you had written in the comic. And I just watched this on feathers js, very cool.
This makes it more clear why MDG is now pivoting.
I read on crater.io that the pace of MDG’s dev has been slowing down significantly. Is it true that the project is down to one MDG team member focusing on the product and for 1.5 that focus is 100% Apollo?
It would almost be worth it to leave Meteor just to be free from debates about leaving Meteor.
@eddyborja - The majority of us are using Meteor happily and productively without being active in the forums.
Agreed 100%
My day job is being part of a team building an iOS and Android app - we love Meteor. We would not have been ready to release our app if we had to maintain 2 native (Objective-C, and/or Swift, and Java) code bases. Not to mention how out of sync they would have become over time, (which happened before we switched to Meteor) and the need for separate developers with strengths in iOS and Android dev languages.
For the company I work for, Meteor has been a {insert-favourite-diety-here}-send … and we’ve also attracted more investment dollars simply because we’ve been able to iterate so quickly, and with hot code push, send the latest demo version to board members and investors.
Yes, we still use Blaze for templating, but use a Framework7 package for styling etc.
But our devs know Blaze (with all its faults 
) and have produced an app that runs on iOS and Android (and the web too) and feedback from our industry has been very positive - we’ve signed up (as far as I hear the sales team talking around me day to day) about 23% of the total market in Australia so far.
And we’re about to release V2.
So my takeaway from all the Blaze / React / Apollo (what?) stuff is:
It has worked for us in the past.
It is working for us now.
It will work for us in the future.
On mobile, we’ve obviously had some issues, but nothing that has been a killer and there has been nothing we haven’t been able to resolve - whether we chuck out an Atmosphere package and replace with an Npm or whatever.
We’re still committed to Meteor the way we use it now, ie: Blaze templates + Framework7 layout + MongoDB (3.2 on the server)- we’re at Meteor 1.4.1.1 at the moment and everything still works.
So to answer @almog original question - “Is it time to leave Meteor & MDG?” -
No, not for us, at this point. Who knows for the future, but at this time, everything that we have built runs well so we see no reason to change.
Absolutely agree 100%
I’ve done that.
And honestly?
I’m 56 years old, and goodness, for me, evaluating all the other myriad offerings out there,
what a learning curve!
I don’t really feel the need to try to learn all that when I know (now) what Meteor (+ packages + Npm (now)) can provide.
So I’m sticking with Meteor right or wrong for the forseeable future - but I’ll be dead soon, so … 
Unfortunately I have to read the forums from time to time to look for people’s advice on specific technical issues related to Meteor, but I try to rely on other sources nowadays.
I’m going to lock this thread, since the discussion seems to have finished off - Discourse allows you to start a new thread as a response to any post, so do that if you want to reply to something in particular.
