Almost one month ago @gschmidt announce the future of Meteor’s view layer. The fate of Blaze seems to be decided. Blaze will be depreciated and in its place Facebook’s React will be the new rising star for a time.
Of course there’s still a question about truly integrating React with Meteor, and further what this integration mean for Meteor general.
We know that React, and the other tech from Facebook that complements it, like Flux, Redux, Relay, and GraphQL et al function in a fundamentally different way that Meteor today. React specifically is geared more towards a functional style of programming, which is very different way of solving development problems. Further, it seems reasonable to conclude that MDG will integrate tech that complements React into Meteor too at some point.
There seem to be many tradeoffs moving from Blaze to React: better component support, yet more complicated, less accessibility, yet more maintainability, etc. I won’t get into the merit of the arguments for or against here, and I think this thread should refrain likewise.
The bottom line is Meteor as we know it, could drastically and fundamentally change in a way that little resembles what we see today. This means the Meteor we all love and are very productive in today, could be lost.
How viable/feasible do you think a Community-Driven Meteor Fork would be?
Would you fork everything or just Blaze/Tracker to start?
Do you have advice on how to get started, how to organize?
Please share your thoughts and opinion.
Thanks,
Aaron