I bit the bullet and started learning React this weekend, so that I could work my through the todos app to compare and contrast Meteor with Blaze, Angular, and React. I have been learning and working with Meteor for awhile so Blaze is rather a natural thing. I should also say that it is quite straight-forward and easy to learn. I have been programming in Angular even before I started working with Meteor so Angular poses no big problems, plus Uri has done a great job of integrating Angular with Meteor. So my question is more due to my experience with Angular and Blaze, and inexperience with React.
Why do the queries have to be resolved to an array in React, i.e., find.fetch() as against cursors for both Blaze and Angular where only find() is needed? Pros and Cons?
I know that which is better is a subjective opinion. Are there any deeper and more technical reasons? Architectural reasons? I will put in more time in Meteor React if there are solid practical reasons to do so, otherwise Blaze and Angular work fine for me. What is great is that you can mix and match both Blaze and Angular which is very nice.
Oh, by the way, checking out the ECMAScript2015 features was another motivation in doing Todos in Meteor React. I am up to step 8, and things work great. The integration of ECMAScript2015 into Meteor is totally transparent, which is how it should be. Great work, Meteor team.