https://twitter.com/arunoda/status/1264937838631665664?s=21
Interesting to see the results.
7 Likes
Funny, he still remembers us 
Did he get bored with NextJS in the meantime? 
2 Likes
So, a Meteor is a prototype toy and a Next is a serious engine for adults guys?
funny 
I don’t understand one thing, if you have to do everything by hands, why is Next needed at all?
5 Likes
Can we relax the NextJS hate.
14 Likes
Yes, please!
If Arunoda decides to do some more work on Meteor, just think of all the amazing things he can bring along from his learnings from working on Nextjs. Best of both worlds! Let’s not discourage that!
4 Likes
Yeah! I got this
So, a Meteor is a prototype toy and a Next is a serious engine for adults guys?
Oh! I didn’t say that exactly. Frankly, I’m not sure what happened in the Meteor land in last couple of years.
We already knew problems of Meteor etc.
I think the main issue was the tight MongoDB integration. Most of the companies who adopted Next.js already had their own data layer, so integrating it with a simple framework like Next.js is a no-brainer for them.
On the other hand, other set of users like to use CMSs. Then Next.js/Gatsby is a great combination.
We still see a lot of companies still use polling for make near realtime changes. I hope it’s easy to manage that in the infra side.
I also think, it’s about the timing and focus as well. Next.js focus on only one thing.
Serving pages. And it does that really great.
About timing: MDG started to focus on Apollo and Next.js joined with the React hype.
Also I didn’t even involve with Next.js for the last 2 years. I was so busy working at Vercel on Infra.
But, I just felt it’s time to do some open-source contributions.
26 Likes
At the company I now work for, this low level consideration is the primary driver of tech decisions. Technically, we could use Meteor, even when not using Mongo. But they won’t even look at it, because it seems so full stack. The sad thing is, Meteor’s vertical integration (primarily its build system, and legendary backward compatibility which makes evergreen development such a breeze) would save everyone a lot of time. It’s just a hard sell without that focused purpose messaging.
9 Likes
I missed you!!! Welcome back 
Have you been working with GraphQL much the last little while? Your learngraphql course is what originally got me interested in it back back in 2016, and have been working with it full time since 2017 or so.
It was a huge inspiration for me, and you’ll always have my appreciation. Thank you so much!
2 Likes
Your information is way out of date. Meteor is doing just fine now thank you.
The main problem we had over the last few years was wasting our energy dealing with losers spreading anti-Meteor FUD.
It is also unfortunate that a personality cult had developed around your name and a number of people reacted with ongoing public expressions of hysterical mourning and gloom after you announced your departure.
Both those groups of people are gone and we have been enjoying peace and progress again thanks to all the loyal long-time contributors and the new leadership of Tiny.
Since we began using Meteor in 2015, it has remained the most productive framework we have ever used to build webapps.
Here in Australia, my business has been using the Meteor classic stack (Meteor, Blaze, DDP, Pub/Sub, Iron Router) together with MySQL. We have implemented several commercial web apps that are used for tracking delivery drivers in real-time all over the country with infrastructure costs 10x-100x lower than our competitors.
I appreciate your past contributions and welcome you back. I have one polite request:
Please use your influence and talents for iterative, incremental improvements that remain true to the original vision of Meteor. We don’t want to lose what we have and see Meteor transformed into a different product under the same name.
If you want to pursue your own vision, it is better than you create your own fork under a new name.
10 Likes
Welcome back Arunoda! I’m personally really delighted to see you here and very grateful for your work.
A lot of good things happened, I’ll try to summarize what I remember:
- Differential bundling (which is awosome)
- Dynamic imports
- Support for React, Svelte, Agular, and Blaze (which is still great, all supported views have tutorials)
- Support for SQL with real-time
- Much faster build times and MUP support thanks to zodern
- Scaling with Redis (while maintaining the same API), using RedisOplog
- SQL like relationship query using Grapher
- Latest NodeJS support with easy update
- NPM support
- SSR support was added
- Acquired by Tiny, new website and pricing model for Galaxy, and new features are being added
- MontiAPM was created based on your great work on Kadira, which I highly recommend
- SimpleDDP was created which is my favorite DDP client, I use with PWAs
- Meteor dev tools received an update
- Meteor Community Formed, which has a newsletter that I highly recommend
- filipenevola joined as a Meteor evangelist
- Many profitable businesses were created
- Any more new packages/tutorial (NPDev React Loadable, Meteor Elm, Svelte/Meteor tutorials, reactive aggregate, and many more)
- And other features and community contributions (others, sorry if forgot your contribution, please share it, a lot of stuff now that I think about it)
And the incredible thing is that all those features were added in a backward-compatible way, a real engineering achievement, I think, given how much JS and the rest of the ecosystem changed, thanks to the genius of Benjamin, one of the best developers I’ve ever come across, and also the contribution of many community members.
In my opinion, the main problem with Meteor that it was way ahead of its time and a very ambitious project, developing very quickly, and wasn’t given enough time to mature (de-couple the architecture, support other DBs, and correct the flaws, etc).
That seems very true but a lot of us (at least here) want to serve rich applications/apps and not just pages, and would like the framework to handle more. I really hope this doesn’t get interpreted as NextJS hate.
I agree.
Once again, good to see you here Arunoda, you’ve a big fan base of your work, myself included.
P.S for a more complete list please go here.
23 Likes
If you want to pursue your own vision , it is better than you create your own fork under a new name.
I think his blog post there is pretty precise. Meteor has not moved much since then and the comunity is still fragmented (react vs blaze vs angular vs vue and ddb-pub-sub vs graphql vs grapher or even vs ddp-method-calls).
I think its now a chance for meteor to unify the community once again, go back to the roots, be more opinionated. Move good community packages to the core (grapher, a router?, redis-oplog (optional)), fix the datalayers problems (global nature of mini-mongo, no strong type support, sometimes awkward integration in ui-libraries) and have every important package be maintained.
5 Likes
Yeah! true that. I have seen the same comment in other places.
Oh! Very sorry If my commented made you angry.
If you want to pursue your own vision , it is better than you create your own fork under a new name.
There’s no need for such thing. We never even looked for that option even in the past.
As you already know, I have moved on due to various reasons.
I just wanted to say hi to some old friends. That’s why I am here.
17 Likes
Thanks for the details.
I didn’t know about https://montiapm.com/.
Wow. Thanks for anyone who’s maintaining this.
I really want to give it a try.
11 Likes