Meteor Gripes

meteor

Next.js, 'Create React App', GraphQL, Redux, and Reactjs - Why not go with the full Facebook stack?
I think moving to NPM is not too late. Meteor still better compare to Create React App or Next.js especially for stability, maturity, and feature richness for building complex app (reactivity, account integration, more broaden supported view engine, etc).
Grapher
Opinion about next.js: Having done a lot of PHP in the past, next.js seems more like a wrapper around React and a few libs so that you can develop faster: filesystem-based URLS —> /pages/about.js renders in /about. Nothing amazing there, we use expressjs for our website and have the same amount of control. I guess we are in 'Run after the next shiny thing mode'.
MDG stops work on Meteor core tech (Blaze, DDP, Livedata, Tracker, etc) and moves almost all their engineers to Apollo (a Facebook's GraphQL overlay) (with considerable pushback from community). And pushes Meteor devs to embrace Facebook's Reactjs (with considerable pushback from community). And slowly, pushes any new Meteor core tech work to community (with mixed results).

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License