We will support Meteor 1.0 for at least 6 more months guaranteed, this was posted in a different thread about Galaxy.
1 Like
Don’t get me wrong, my main gripes have nothing to do with the stack in itself. If React is the next shiny thing, by all means let’s run after it.
sidenote: (I’m coming from a Flash/Flex world, dare I say it, where all the ‘chasing the magic’ has been done before with kind of the same outcomes btw :), all the magic stuff of React/Redux/Blaze/Etc… has already been done in another Ecma language, Actionscript, many times in 100 different ways. But let’s keep busy nonetheless. We need another wheel 
).
What I meant by being dissapointed, is by the (for me at least) total chaos the eco system is in. It used to feel well taken care of. Lately it has more of a feeling of something that is (kind of) without clear direction. I’m not sure if I’m an old guy yet, but in my experience that’s not a good sign if you’re thinking about adopting Meteor.
Some examples (if I’m talking rubbish, I’m sure someone will put me in my place):
- One post of Geoff, getting a lot of people “upset”. Then… nothing. For a long time
- His collegues do chime in, but seem to be contradicting what Geoff said (I would assume everybody would be on the same page?)
- Although @sashko is right that you could still use Blaze and that it’s still “supported” (thanks btw), most people will still run away from it as fast as they can. It’s been called a dead-end by Geoff (and others). So now all available packages will be in flux as well… who knows which ones will be updated later on.
- The guide (which was great) feels outdated even before it was coming out (not saying it’s not relevant at all, it just feels weird if someone said we’re all going “left” and the guide is still being worked on going “right-ish”).
- All this focus on the view layer, when there were so other (maybe just as important) issues still unworked on. E.g. an already started SQL innitiative (great!) which was then just left to… die? Nothing, nada. No news, no plans, nothing.
- Galaxy… who knows what is going on with Galaxy. No idea. As an outsider? It feels like it’s having a hard time getting up to speed and every available resource is being put on it to get it right. Note: Totally clueless here, so no basis or facts whatsoever. That is probably one of the reasons why Meteor is getting less (is it?) attention.
For me, the only real value I can think of that’s left (for the time being) is a nice integrated build environment. But that one makes me feel silly if I wait for 30 seconds on every file change, and reading Webpack people doing the same thing (and more) in 2 seconds per file change So that value is relative as well lately.
After typing I feel like an “old man” complaining/whining. But don’t get me wrong, the original idea of Meteor was great and made me start using it. I’m hoping it will succeed, so that’s why it is so frustrating to see it in it’s current “state”.
4 Likes
It’s a fact that the conversation on the forums is not representative of all of the people successfully building great apps with Meteor - the number of users that have ever visited the forum is a small fraction of the overall Meteor user base, simply because not everyone is interested in having lots of public discussions about their work tools.
10 Likes
That’s true, and a good reminder for me to keep that in mind. But in this case, I meant I was wondering if the Meteor codebase (platform) wasn’t getting all the love and attention it once got (from e.g. MDG). Even after it has been left in “flux” (no pun intended) by announcements like the one that started the thread.
Good summary @Ben.
Two things I can think of right now to add to your list:
-
I think it has been hinted at by @evanyou that with the depreciation of Blaze, Tracker’s future is also uncertain.
-
Some developers of merit have characterized MDG’s new strategy as a “distribution” of up to date JS tech, instead of a JS framework.
This is a quote from @sashko that I think sums up the recent moves by MDG:
@sashko, maybe my question should have been, what parts of the stack is MDG going to build and what parts are they going to “outsource”?
I mean, we know that once Blaze goes, Tracker will follow. What will fill in that void? Is MDG going to take one or more of Flux/Redux/Relay and shoe-horn it into Meteor or will we see something custom from MDG?
And to continue, with Blaze and Tracker gone, when will Sub/Pub be put out to pasture? And what are the plans for the replacement?
And further, once Blaze, Tracker, and Sub/Pub are gone, and with GraphQL on the horizon, how long will Mini-Mongo have left in this world? And here too, what are the plans for replacement?
Further, I’ve heard you say on other threads something to the effect that due to patterns and practices around React not being fulling flushed out within Meteor, the Documentation and How-to around the UI are not in place. When will we see something on this? Is someone flushing out these patterns and practices?
The migration from Blaze to React. I know I’d love to see documents from MDG on how to replace portions of a Blaze template with a React components and all that entails.
Thanks for everything so far @sashko! 
1 Like
Hey, just curious (I don’t want to start new topic). What’s the status of this ‘Standalone Blaze’ https://meteor.github.io/blaze/ project? 
It is so old, but really cool
2 Likes
Fantastic work. 
Keep it up!
Agreed. I find the forums overly negative the majority of times.
5 Likes
so you can use Tracker with React without getting unnecessary rerenders? I’ve fiddled with fine grained reactivity in React for quite some time now, and I can’t seem to get Tracker to rerun computations correctly. Please, enlighten me…
Simply look here:
Full stack redux tutorial
For something so, so simple and trivial 150 screens of code and explanations - it’s just ridiculous!
Blaze 2.0 need to be Fast, Simple, Functional, Easy to Learn and Usable in 90% of the Everyday Scenarios and need to take only 10% of the time vs React and Redux.
2 Likes
Blaze-React is ready for review, we’ve got most of Blaze 1 functionality. I hope you like it
Will probably work on building a template parser for react using the learnings from this project. That might be a great continuation of blaze, if not people find this package really useful.
Have a great weekend!
11 Likes
It’s the downside of success and popularity. You can make some of the people happy all the time, all of the people happy some of the time; but you can’t make all the people happy all the time.
Fantastic news. I’m making a push to finish up the Checklist Manifesto (the FDA/HIPAA version of the Todos sample app). When that’s done, we’ll have validation test coverage across the app, and will be looking at refactoring to 1.2 and Blaze-React.
4 Likes
Has everyone seen this?
https://forums.meteor.com/t/angular-react-and-blaze?source_topic_id=13561Seems definitive to me.
Where’s proof that that will happen? I don’t see why it will.
Since Blaze seems to be back from the grave, nobody knows.
Until next 180° turnaround.
1 Like
I’m in multiple communities and my comment was based on the fact that the Meteor forums are by far the most negative of the lot.
2 Likes
I too feel like there’s some excessive negativity here based on rumors that have apparently manifested out of thin air. Or have I missed some official announcements?
Really ? When ? Will you be using Vanilla React or tim’s package ?