I've been working on Meteor apps for a few years now, and my TLDR answer for you is, no, don't use it. The releases since 1.3 have definitely pushed it in the

I've been working on Meteor apps for a few years now, and my TLDR answer for you is, no, don't use it. The releases since 1.3 have definitely pushed it in the right direction: * NPM instead of atmosphere * React/Vue/whatever instead of Blaze * ES Modules (import/export syntax) in place of global variables everywhere and a dependency loading system that i-shit-you-not came down to loading things in alphabetical order * ESNext support * Getting Node and NPM up to current LTS versions Next stop on their roadmap is integrating Apollo, at which point it'll basically be a turnkey system for building React/Vue apps on top of GraphQL. Most of what originally made Meteor what it was will have been removed in place of sensible best practices that everybody else in the JS world has since moved on to. But for me the sticking point is that Meteor is built on a couple of assumptions that, in my humble opinion, are fundamentally incorrect. 1. Focusing on writing code that runs on both the server and the client is a useful idea. 2. MiniMongo is a sensible way to handle the data layer and reactivity everywhere is helpful. I personally reckon these are both crappy ideas, and combined with the "magic" parts of the framework, they encourage people who are new to full stack JS to develop bad habits and skip learning some of the real fundamentals that every developer should know in relation to security, performance and scalability.