Angular, React, and Blaze

[aadams]

[quote=“dfischer, post:132, topic:16100, full:true”]
I’m a bit confused, so is Blaze going to be actively maintained and improved upon, or just left around and used for guides?
[/quote]Hi @dfischer, you might get a MDG response, but incase not, this comment just yesterdays seems to suggest the latter:

@gschmidt

We’re going to continue improving support for other view layers (Angular and React) until they’re at parity with Blaze, including the Guide. In the longer term, we expect that most of the usage will gradually shift from Blaze to Angular and React. How long MDG maintains Blaze will depend on how much usage Blaze continues to get in the community, especially among our business customers.

We can only guess what MDG means by “maintains” above.

My guess is “maintains” to MDG right now and in the context of Blaze means they’ll keep Blaze under their control and nothing else. Not fully open source it. Not allow the community to drive the direction of change or fix bugs. Hopefully this is a temporary state, but it could very well be permanent.

An adjacent guess is Blaze will be frozen as it is today and depreciated slowly, not dropped outright, only due to the: lack of proper Meteor React/Angular integration generally, lack of proper Meteor-integrated package coverage even at the basic level in some cases, lack of written guidance for Meteor React/Angular, and finally legacy Blaze customers and developers.

---

This comment seems to suggest Tracker and Blaze as stand alone, open sourced, community driven projects are a possibility (fingers crossed):

@gschmidt

The improved npm support in Meteor 1.3 is a good next step. A later step will be to release the Meteor core packages themselves in npm.

I think Tracker and Blaze would be a great contribution to open source by MDG.

Hope this helps.