I’m on the fence. I think Blaze is great and I use it daily in the big app I’ve been building at work. I’ve never built anything more quickly than I have with Blaze. It’s simple to learn and easy to use. However, I also think that React is simple to learn and easy to use (in Meteor — it’s mega complex on its own). It’s also much more stable and capable than Blaze is. Right now you can incrementally load React components per route and do all the things you want Blaze to do. We don’t have to wait.

This is a question that I think about all the time. While working I spend all my time with Blaze and when I’m messing around it’s usually with React or Phoenix. So, the majority of my time is spent working with Blaze. I say this to make the point that I’m not unfamiliar with it and that I spend a good amount of time working in it so when I advocate for using React it’s not because I don’t know how to use Blaze and have never experienced its goodness. I have, and I still think React is a better choice.

On a side note - I think The React ecosystem desperately NEEDS something like Meteor. Lately, many people have been making a stink that React is really hard to use. This is true only because the tooling around React is terrible and not because React as a view layer is hard. React needs conventions for building apps and I think Meteor is in a great place to provide those conventions. I hope MDG can take advantage of the opportunity.