I am also frustrated with all this Meteor platform volatility nonsense.
Blaze meets a need. It’s simple, easy to learn, stable, and an effective tool. You can build re-usable components. For many apps it’s all you need. Why Meteor would so quickly abandon this technology baffles me. Yes I use the word “quickly” here - I know it’s been like a whole year since 1.0 was released (I think it was Oct 28, 2014). But to me it feels like the paint on this shiny framework just dried and now we’re redecorating. WTF?
But of course it’s really not about Blaze or React or Angular or whatever the next thing is… is it?
It’s about users who use your application. You know - the one you’ve built or are currently building. And the entire developer community - a number of which like me are all about using a great tool to build great stuff and NOT about adopting new technology for technology’s sake.
If the tools you’re using to build this experience are sitting on a sea of shifting technological sand - everyone loses.
Instead, I’ll argue MDG’s focus should be on responsibly evolving this awesome framework in a way that doesn’t leave developers in the dust.
A few facts (according to me) to ponder:
- Meteor will never please everyone
- Having an opinionated framework that is the best tool available for certain type of jobs is a good thing
- Quickly adopting new technologies at the expense of obsoleting apps already built on the platform is a bad thing
Meteor got a few things right (reactivity, data on the wire etc) where other frameworks missed the mark - that’s why we’re all here.
I’d like to see more leading and less following going on around here.