Iâve read this post. This discussion and @nosizejosh info about tweet from Taylor Otwel inspired to me to write this article.
By the way, when we started to cooperate with corporations, and outsource projects for them using Meteor, is was something fresh. Not only for us, but mostly for them.
If the corporation has its own dev team, then they usually use older solutions and technologies. Itâs not someoneâs fault, but only a fact.
When we come to them with Meteor, it turns out that our develop time is almost half as long as theirs.
Meteor is amazing stack and like many of you said give very good flexibility.
6 Likes
Totaly agree with your comment. Meteor is losing focus going after Apollo and GraphQL (It is good to have others alternatives). Focus on React and left Blaze, it is all the reason that many developers choose Meteor. It is very frustrating to see Meteor left those. They should give all efforts to improve Blaze and Meteor core packages. 
1 Like
But there are many happy react, vue, angular, graphQL users on this form as well who welcomed and embraced the flexibility. A lot of folks clearly appreciate the openness and integrations with the wider ecosystem.
1 Like
Qualia is still loving Meteor 
14 Likes
Yep (all three of our products ). We have some micro-services to do document generation and random stuff like that, but all user facing stuff is in Meteor.
Itâs a bit outdated at this point, but I gave a talk at Meteor about Qualia https://www.youtube.com/watch?v=Iguedyg2cOI
I can legitimately say that Meteor has been an important factor in our success so far.
18 Likes
As I see it, this happened:
Many people had just gotten into Meteor and loved it because of how fast you could create a fairly advanced, interactive, website. Meteor took care of almost everything, you just needed to write code almost wherever and however you wanted. If you needed extra functionality you headed over to Atmosphere and grabbed it. It was easy to learn and it was easy to teach.
Then suddenly everything changed.
In hindsight, it did not change at all, we were just given the options to be more âindustrialâ with our structures and was also given options to choose frontends. Meteor got better, but it did not feel like that. I think it was down to a bad communication strategy from the MDG, because myself and many with me got the feeling they said âyou are doing it wrong, this is the way you are supposed to do itâ. Suddenly Blaze was dead and it was all about npm, React, Angular, Apollo and whatnot.
There is a time when you learn and there is a time when you produce. In the middle of your production you do not want to hear that the stuff you use are on a death list. In the middle of production you do not want to change the development strategy in a direction which contains mostly question marks.
I think MDG made the right choices, Meteor as it was could not go much further, but they should have been more gentle, they should have marketed the ânew wayâ as an alternative for those who wanted to do a more proper architecture without signalling the death of the old way. Especially since that is what it was. The old way did not die. Maybe it never will.
The new way is better, but different. It is a bit harder to learn but itâs worth it. For some. For others, the âold wayâ is unbeatable. âYou need a site for your cake recipes? With voting and comments? Facebook login? PDF printouts? No problem, you have it in the afternoonâ
6 Likes
What is meteor other than a build system and an easy-to-use (but not necessary to use) account system (and a jumble of additional packages)?
Add on top of that Reactivity and Optimistic UI powered by minimongo.
3 Likes
Iâve found meteor a couple months ago. I studied it, learned it, practiced it a bit. I loved the meteor approach, specially Reactivity and Optimistic UI out of the box.
Iâm about to create a proposal for an App with potential 10 years life. I do not see new posts from MDG, or new great enhancements, and roadmap, at least I can not find it. Do you guys can lead me somewhere to support my proposal?. Since I have not written a single app yet, I still wonder if Meteor is the right technology for the next 10 years.
Any comments on this?
1 Like
Will you share some of your data, what you measured? I was thinking of using Gasby for static websites, but Iâm curious how Meteor performs.
1 Like
I donât think anyone can speak with any level of confidence on the state of a particular piece of software 10 years in the future. That being said I think that Meteor development is still going strong with MDG and the Community doing lots of awesome work. I personally donât see Meteor falling by the wayside anytime soon.
5 Likes
@copleykj, I agree.
When things started really changing around Dec. '15, I was cautious. Then over the course of a year or more, as MDG move away from Meteor and focused on Apollo, I became worried this framework I invested so much in would enter a slow decline.
But in the last year or so, Iâm pleased to see that Meteorâs development as progressed nicely with @benjamn @abernix & @hwillson at the helm. And the clip of progress has seemed to actually increase, with MDG opening up to PRs from the âoutsideâ. Impressive.
8 Likes
Been building apps with Meteor since '13. Never been let down by the framework. Old apps still keep working, new stuff is easier to build than ever.
I think that, like with most good Open Source Software, the question is not whether itâll still be there in 10 years, but whether itâll help you grow with it or it is going to leave you behind.
You will be growing with Meteor.
6 Likes
Itâd be great to get a wrtie up on this.
In the meantime, React Static is pretty sweet too - and in some ways better than CRA.
(this is not to speak against Gatsby)
1 Like
Here is the Meteor roadmap: https://github.com/meteor/meteor/blob/devel/Roadmap.md
You might also check out the feature requests to get a better idea where in the short and middle time range Meteor will be headed.
4 Likes
Whoa, very optimistic approach. Personally, I donât know application built in one technology and lasts - in the same terms - for long time like 10 years (wait a second, I know - and it is called Basecamp, but I can be wrong). Every application needs to evolve. If you will choose PHP, Ruby or Python - you do not know, if it will last for such time period. You do not know how it will look in next decade. Thatâs why I would recommend you to think about shorter period. We donât know, what the future will bring to us.
Because that place is full of Meteor fans (like me, @CatInBlack and others), I canât write other words - donât be afraid of using Meteor in long-term development. It is very mature technology, built by great developers (@benjamn and @abernix, I am looking at you!). Maybe three years ago, it wasnât, but now - everything is in great shape. I would recommend it! Of course everything is up to you how you will prepare and develop your app, but I think - if you will follow the Guide - everything will look fine and clear. Donât be afraid of MDG disappear - it wonât. They gained a lot of money some time ago from VC and contracts simply do not allow them to forget about their product and clients. Maybe they do not always update their blog and website, but they are alive - and I am sure, that they will for next decade (remember that they are working since 2012!).
So, follow up the MDG and move your next big project towards with Meteorâs help. You wonât be disappointed! 
3 Likes
I just recommended Meteor to a customer today. For me, itâs still the best all-in-one JS framework out there.
12 Likes
My two cents : started using Meteor in 2012, less than one year later it had become my main development tool and I would not trade it today for anything else.
Above all, Meteor helps me focusing on creativity, juste like Logic for music or Unity for 3D : easy learning curve for the first steps, and immense possibilities under the hood. The project I will release in the next coming months, a full social network with realtime collaboration features, is the most ambitious one I ever worked on - and it would definitely not have been so easy to develop in a small team without Meteor. Iâm very thankful for that.
Just hoping they will seriously reconsider the case of Blaze : like it or not, its simplicity plays a major part in Meteorâs attractivity 
6 Likes
Hi,
What was happier with the meteor was for the simplicity of developing a complete, responsive, modern and quality code. And I did with the basics, meteor, iron and blaze. I even managed to generate the Android and IOS versions without difficulties, a plus in the framework. I do not intend to change the structure so soon, but for new projects I do not know what to actually use. For while the diversity of choices becomes good, it brings back, as someone up here said, a need to learn various other things.
In my opinion, the Meteor should have all these possibilities, but it should have some standard framework definitions, to ensure continuity for projects that use them, as this is critical to corporate projects.
1 Like