What do we the community do with Blaze?

I’m also interested in this. I have a long standing love affair with blaze.


He’ll come back saying it’s a huge risk. The reality is that it’s not.

AirBnB is using it. If Facebook was trying to use react as a way to sue and take over startups, they’d have taken over AirBnB and be reveling in the spoils…

and they’d have done the same with Asana, Atlassian, BBC, Chegg, CloudFlare, CNN.com, Codecademy, Coursera, Craftsy, Dailymotion, Dropbox, Expedia, Facebook, Feedly, Flipboard, HipChat, IMDb, Imgur, Instagram, Khan Academy, KISSmetrics, Mattermark, Minerva Project, Netflix, OkCupid, Rackspace, Rally Software, Ralph Lauren, Reddit, Redfin, Salesforce, Squarespace, The New York Times, Trunk Club, Twitter, Uber, University of Cincinnati, Venmo, WhatsApp, Wired, Wix, WordPress, Yahoo, Zendesk and everyone else using react.

But they haven’t.

So I think the 99.99999999% of developers using react on their revenue-less startups will most likely be okay… worrying about this is analysis paralysis at it’s best. analogous to fretting over unit tests for every single function in your MVP.

Beyond react’s utility to facebook and their type of app, most likely Facebook is putting react out there hoping it is widely adopted for other reasons. For one, it makes acquisitions 100X easier when the company you’re buying uses your entire stack/philosophy/architecture that you use.

Full Disclosure: I don’t even use react. I use Blaze and love it.


Man, I actually REALLY like blaze, I think it’s extremely well designed for usability. I find most other frameworks out there have a ridiculous amount of background before even making something as simple as a list from a query with a search box.
In blaze? Maybe 1-2 minutes of programming.

I’ve tried react and it is extremely… meh. Angular2 is okay, but a little wonky.

What is currently limiting blaze? Why do people prefer other frameworks?


Blaze is OK, but MDG was consuming too much resources on it. They decided to stop investing time and money on Blaze when huge companies like Facebook and Google are developing view layers as well. One great thing with React is React Native: hardware acceleration on mobile.

Personally I think React jsx code is a mess you can’t read, so I moved from Blaze to Vue.

1 Like

yep! Here we are! :slight_smile:

1 Like

Well, there’s a new repo, slack channel, and forum category now, as linked above! Sounds like people are pumped about getting a community together.


I am glad to see all this enthusiasm for contributing to Blaze. I think at this moment we are still stuck at waiting for MDG to allow external Blaze repository to work with current releases. And to move stuff to NPM, but once we get to there, I think we are then open to start evolving Blaze further.

Feel free to open issues at https://github.com/meteor/blaze with ideas what should be next things to work on.

Well, there’s a new repo, slack channel, and forum category now, as
linked above! Sounds like people are pumped about getting a community

Somebody can make a pull request and add links to all that (and auto-invite Slack button for channel) to README at https://github.com/meteor/blaze.


Yeah, FWIW it’s one of the top priorities at the moment, after fixing up the bugs found after 1.3 launch: https://github.com/meteor/meteor/blob/devel/Roadmap.md

Where is the blaze channel? What slack domain?


Who is the slack admin to send invite or to setup an invite page?

Whoops, sorry should’ve posted: http://slack.blazejs.com/

Yes. This is while we are waiting for that, we can start planing and making design ideas. For example, we still do not have an answer to:


Well, it looks like somebody did it :wink:

1 Like

I created also the proposed first steps roadmap: https://github.com/meteor/blaze/milestones

So that is clearer what I think should be the first steps to do. Some depend on MDG improvements to Meteor codebase, but some can be done independently (landing page, documentation system).


damn right! its lack of information…
its going to be cool for new players to accept Blaze’s way that is most splendid part on Meteor!
im in if u need some hands-


Can you get hard numbers from the /.meteor/packages file ? It would be very useful to know who is using what. Meteor already connects to the web for updates, it could by the way report what packages are installed if not already the case.

I believe a lot of people haven’t migrated yet - I haven’t, was waiting for the whole React vs Blaze argument to calm down. Also, I missed the conclusion of the Blaze2 announcement / discussion : is MDG going to add a layer on top of React to make it easier to use or not ? Last time I had a look to at React, it was terribly verbose and the simplest tasks looked like Java GUI hell. I was planning to migrate to both React and Apollo at the same time if possible but no dates were given for Apollo or Blaze2 / improved react.

Conclusion was posted here: Angular, React, and Blaze

Blaze will stay as Blaze, React as React. Apollo is apparently some months away from completion but initial implementations are likely coming soon.

The answer is definitively no on this one.

I think @manuel is working on a ViewModel for React :wink:

1 Like