Oh man, that would be great - really.
A few months back, I determined that Blaze might not be making it - and for various reasons I spoke with my client for the main project I'm working on now and we decided for me to take a month or so off and learn react and then come back and refactor the whole project. I'm almost done with that (Actually, I think I'll be back where I was by the end of today). And I have to say, I feel much more better for it. Learning any new JS technology typically makes you a better JS programmer, and I for sure feel like that's the case with React.
HOWEVER... if I felt like Blaze was going to have a future like it might have now that we've made these moves back then - maybe I would have just stuck with it.
I think this will have a great impact for those who've learned "Meteor" and are happy with Blaze. Especially those who can't just take a month off and pick up React. Granted, maybe I went overboard with my React training, I'd say you could probably get by with taking a week off
All and all, I feel like this is a really good thing you all have done here making blaze it's own thing.
+1 for bringing Virtual Dom to blaze - Even though I am a React developer at heart now - I was once enjoyed Blazing it up a long time ago. And from my Blazing days, I feel like there is something Blaze still has to offer the scene.
There is something about the flexibility of Blaze/Meteor/Session on one side of things and React/Redux/Meteor on the other. For example (now, this might be wrong for several reasons - but I'm bringing it up anyways) I like how I can just import
Session on the server where I have a method to insert some data into the database... And if I find that the user is not logged in - I set a Session variable which in turn triggers a "login" modal screen to request my user to login (I throw an error also right after that Session.set). I agree, that I should be checking for this on the client side - and I actually am. I just like the fact that with Session - I CAN do this from the server. And my component watching that Session variable still gets "re-rendered" because of the createContainer context - so, in effect - it's kind of like redux, I know it's not the same for a lot of reasons - but this way just seams simpler to me for now. And that's what I mean - I like how with Blaze/Meteor you can just "do" what you want to do sometimes, yes I like the structure of React, it's made me a better developer. But sometimes, freedom feels good, and get's the job done.