Why doesn’t MDG just adopt Vue.js and forget about React vs Blaze?
Wednesday, December 16, 2015
With all of the discussion surrounding what is going to happen to Blaze and how soon React will be the default UI layer of meteor, why is everyone ignoring vue.js176?
Reasons why vue.js should be considered
- Vue is maintained by a core meteor developer.
Evan You created and maintains vue.js, and is a core meteor developer. This gives him insight into what meteor needs, as well as having an independent, agnostic UI layer (which I believe is what meteor needs) - Similarity to Blaze
The syntax for vue.js is extremely similar to blaze. In fact, it seems like a perfect three-way marriage between angular, react and blaze. However, the focus of vue.js is strictly to be a front-end UI built for quick starts and short learning curves. This fits into meteor's wheelhouse perfectly. - Maintaining meteor patterns
One of my biggest issues in using react is that it does a terrible job of maintaining separations of concerns (in a front-end developer experience). While react tries to manage your entire application state through flux/redux, vue.js doesn't care. - Speed/Small learning curve
What many of us may not realize is that one of the main stengths of meteor is that it allows developers with little to no experience learn how to make rich applications through it's speed of getting set up and running. It's why I learned meteor, and why I'm a developer to this day. The front-end UI layer of meteor should be the same and should not require a complete rethink of your application. - It provides possible stability
React is the hotness right now, we can all agree to that. But last year at this time it was angular. Many years ago it was Ember. Essentially, every so many years we see a change it what people prefer. Being that React is going to have to compete with angular 2.0 soon combined with the fickleness of front-end techs, why not just choose a quickly up and coming framework now and make it our own? If not, what happens if the tides turn and angular 2.0 usurps react as the front-end framework du jour?
0 comments