I used to build with Meteor (wrote a long advocacy post in 2015), and ~5 years later, I’m semi-regretting not sticking with it. The main reasons that drove me away were: sense of abandonment, lack of support for PWAs and GraphQL, and team/community split (Apollo? Blaze vs. React?).
As others have said, it may be worth de-emphasizing “easy”, and emphasizing the serious time savings that Meteor offers. I estimate that at the start of a project, Meteor easily saves a man-month worth of coding time not spent reinventing the wheel (accounts, data sync, bundling etc.) with the “build your own car” approach.
What do others think? As long as it’s also emphasized how you can “graduate” from the initial setup (e.g. opting out of realtime data when and where it no longer make sense), I think Meteor has a winning story.
As for,
That’s true, for myself included. But I recognize there my OCD tendencies, However, when you step back and honestly ask yourself what benefits you’ve got after spending hours or days tweaking and testing and debugging your tweak, over the tried & true approach that a framework offers, the answer is often, “not much”. And it tends to be “not worth the time you’ve spent, which you could’ve spent building an actual feature”, when you ask your customers and business stakeholders, rather than your inner developer geek.