It’s been a great progress recently! Thank you very much! Good luck!
1 Like
Thanks everyone. Reading these replies over the past week was the best part of the whole transition.
@harry97, thanks for the words and for all the feedback over the years.
Thanks @leonardoventurini, @alimgafar, @nachocodoner, @italojs, @msavin, and everyone else who dropped a message here.
As you can notice the team is intact and still shipping. The CapacitorJS integration beta just went out, and there is more on the way.
If you want to stay in touch, I am on LinkedIn and X (@fredmaiaarantes).
See you around, and keep shipping.
11 Likes
Capacitor beta is more amazing news. It really felt like Meteor was too far behind standards for years - but now I feel it has been have fully modernized. It’s going to be interesting what ideas @geekforbrains has for the next steps!
4 Likes
Thank you, Fred, for your awesome works.
3 Likes
For the new GM … let’s stop all the social media posts titled “Is Meteor Dead” or … “look, we have a settings.json file”.
All the best to the in and out individuals!
4 Likes
@paulishca I appreciate that feedback. What would you find more interesting or helpful? What do you dislike about the existing material?
Why you should use Meteor to code your apps with style and deploy them for free in the blink of an eye
Why MeteorJS is the stack to adopt for building your AI apps
Why Meteor is more alive than ever
Why Blaze is not only simple but also powerful
Meteor in 2026 for deploying your cross-platform apps (well, we need to finish Capacitor and get the PWA up and running first)
MeteorJS needs you
Some metrics on our Galaxy hosting solution
Let’s compare MeteorJS and other frameworks
The 10 prompts to use for your Meteor apps
Why MeteorJS is the best framework on Earth and why anyone who says otherwise will probably catch a cold tomorrow
etc…
2 Likes
@geekforbrains I wanted to share some thoughts with you, I hope they are constructive. To start, I would ask ChatGPT the following (set it to High or Pro):
“Why companies stopped using MeteorJS?”
It will do it’s thing and it will give you a pretty solid list of reasons why Meteor.js usage declined. I would then reverse engineer that list and integrate with whatever goals Tiny has internally - by the way, it would be really cool if you shared those goals publicly eventually, to the extent that you can.
A big chunk of it is already “solved” like the fibers thing, but if the goal is to make Meteor great again (no pun intended), it would require a pretty solid strategy for tackling what I believe to be a trust and scalability issue.
To put it simply, it’s not easy for companies scale past a given threshold, and those types of companies would be exactly the ones that would be most profitable for cloud hosting.
That could involve the framework re-architecture or it could involve brand positioning, or both. Some of the unique advantages Meteor had will never return especially as the ecosystem caught up.
So for Meteor to be reborn I think it will take some serious innovation and perhaps ride the AI wave properly. Otherwise, it will remain in what I call “life support”, it’s not dying but it’s not growing either.
Meteor does have some pretty unique capabilities that could be leveraged for AI, with some thought regarding real-time. Perhaps the DDP protocol could be expanded? Who knows.
I would love to see Meteor thrive again, and I’m hopeful someone with a fresh perspective such as yourself will help.
Good luck,
Leo
3 Likes