Another Blaze aficionado here! Especially when coupled with ViewModel by @manuel . I’ve been using Blaze since we jumped onboard with Meteor in 2015. In my honest opinion, Blaze works wonderfully with Meteor’s reactivity system and is a very capable frontend rendering system.
We have over 100k lines of code in our app. So far, our codebase has not turned into the feared evil spaghetti monster some people are talking about. I very much build stuff with components just like I would with React.
In the meantime, I’ve written an app with Gatsby (and therefore React) and one smaller app with Vue. I would still pick Blaze or Blaze+ViewModel over React or Vue for Meteor, unless SSR was a requirement.
Blaze might be slower in some benchmarks, but our users are crediting our app for being “snappy” and “fast”. I think most cases of Blaze being actually slow are related to abusing the reactivity system or just doing stupid things or using bad patterns for data loading.
This is where a larger community with a wider variety of tutorials repeating best practices would become very useful for Blaze.
I recently found an issue with Blaze and
dynamic-imports that was caused by a bug in Safari browser itself. The problem is being fixed (or already has) in Blaze right now, so I wouldn’t go as far as saying Blaze is dead. I’d say it is quite stable and capable as it is, since this is the first real issue we’ve had with Blaze ever.
Unfortunately, when separating Blaze from the Meteor core the project was handed over to @mitar who hasn’t really been active in the project ever since. He himself has said he’s working on school stuff and has no time available for Blaze.
Might be a good idea for MDG to appoint a new project owner for the Blaze repo: it might revive the Blaze community or at least get the 1000$ of donations working for the benefit of Blaze users.