I never used meteor, but from what I understand it's functionality was, I currently use FeathersJS + SocketIO + VueJS (and nuxtJS for serverside rendering).
I tried FeathersJS for a recent project but ended up dropping it. Documentation was all over the place, many of the example repos didn't work out of the box, and I found some of their solutions were half baked. I also found their core ideas added as much mental overhead compared to "standard" express routes and so wasn't worth the proposition of consistently setting up routes. Maybe if you came in at the right moment when a release's documentation has settled down, outdated documentation is clearly marked, and a majority of users have settled on particular libraries, but that was not the case when I checked it.
I'm thinking of checking out Meteor now since on balance people here are saying it's good for prototyping at least, and I'd like some real-time functionality.
I built an app that was 90% CRUD a year ago and I choose Loopback, but FeathersJS was on my radar. Loopback did the trick, but I just hated defining models in JSON instead of JavaScript objects. Good to hear FeathersJS on HN. I’ll check out the project again.
I'm thinking of checking out Meteor now since on balance people here are saying it's good for prototyping at least, and I'd like some real-time functionality.