Thinking ahead to Blaze 2.0, I think we should be talking about somehow building off of Vue 2.0 #128 (comment) instead of duplicating efforts or talking ourselves in circles feature after feature, and getting sidetracked or bogged down.
We need to be looking at the big picture. Vue has the momentum in the broader JS community. Vue has the features we’ve been asking for and need. Vue has the performance. Vue has developers working full time on the project. Vue has tempting similar to Blaze. The only thing it’s lacking is tight Meteor integration and maybe a sprinkle of Blaze flavor we are use to around these parts.
I think we should be discussing how to build off Vue with a emphasis on Meteor – as a Blaze 2.0.
I think the timing for a move like this is just right:
- Blaze community driven and looking for change.
- Meteor classic in a state of transition and flux, open to change.
- Vue 2.0 just release with a feature set and performance to be envious of.
How do you think about using Vue as the base of Blaze 2.0? Please vote on the issue and feel free to discuss about it!