[lioeters]

Not the parent commenter, but.. Having only a superficial knowledge of Meteor, I prefer a more modular approach:

- React/Preact with context or hooks instead of Redux

- Micro for server - https://github.com/zeit/micro

- Postgres with Knex for data persistence - https://knexjs.org/

Add authentication, WebSockets, etc., and it starts to look like an ad-hoc framework - except that all layers are generic and replaceable (theoretically) with equivalent features, like using Express or MariaDB.

I'm also quite fond of Next.js, which lets me have all the above. https://nextjs.org/

[aogaili]

Thanks, but the issue with the modular, ad-hoc approach is that you need to do a lot of integration and leg work before you get to the domain problem in hand and you'll need to maintain those integrations going forward.

[lioeters]

I agree, and that might be the most valuable thing about frameworks like Meteor. It provides a curated developer experience, where most of these common features and integrations are solved.

They tend to have far superior documentation than any ad-hoc approach, making it more suitable for teams. And a whole community that continues to debug, improve, and maintain it.

Well, I'm with you in the search for such a framework!

[SparkyMcUnicorn]

FeathersJS + Nuxt/Next (or any front end you want) has been a good combo for me.

Meteor always had a blocking issue for me every time I'd try to use it.

[aogaili]

I like FeatherJS as well.

What kind of blocking issues? you mean getting it to run?

[SparkyMcUnicorn]

Usually it was a feature I wanted to use that was broken. It's been a while, so I forget specifics.

Requiring mongodb was another factor a few times as well. This was before Mongo had ACID transactions or any built-in options to save immediately to disk.