There’s been a lot of discussion lately about why Meteor exists, what it does, what it should be, etc. I wanted to clarify what Meteor means to me: It makes my job easier
What I like:
- Auto-include all files
- DDP (obviously)
- Not having to do exports (Globals)
- EcmaScript in Meteor
- React support
Where does Meteor fail?
Meteor fails me if there is something I have to jump hoops through in order to get working, and costs me time. Specifically, if it doesn’t speed up my development time or make my life easier. Right now for me, this includes:
- Process of adding NPM packages
- Build time
- No component “hot” reload
- No code splitting
- Packages on Atmosphere that don’t work or are no longer maintained
- Can’t easily use third-party React components
I don’t complain about these because they are cool to have or are the latest and greatest. I complain because each of these specific things makes my life easier as a developer and speeds up my development process. I am aware that MDG is working on all of these items, and I can’t wait to see what they have in store.
I think the core vision of Meteor is super-strong, as as long as they keep their focus on making my life easier as a developer, and speeding up my development process, it’s here to stay. Please don’t change either of these visions as your mission by trying to appease the nay-sayers and becoming more “mainstream”. In my eyes, that is when Meteor is no longer relevant to me, when it’s just like everything else.