Yep, I’d like to join, too. But how can I do this?
Until we fix the invitation link, you can DM me your email.
3 Likes
So excited about this!
8 Likes
Fly, little library… FLY!!!
18 Likes
Haha – thanks – that made me smile. 
3 Likes
Invitation limit already reached
1 Like
I hope we will be able to use Apollo with Blaze.
2 Likes
Great news! So happy for this. I’ve really tried to like React and even Angular, but failed miserably. Blaze is still what my heart tells med to use. And this situation may even make Blaze better. I’m a solo dev and doesn’t need all the scalability, modularity and buzzword compability that the large teams demand. Go Blaze!
5 Likes
I don’t like using Blaze, but I still think this is a pretty cool milestone! Good job to everybody involved, I know it wasn’t easy to get here. Don’t hesitate to ask if you think there’s something I can help with.
6 Likes
Is it?
Well, you can still DM me your email if you have problems signing up.
Awesome news!
Unfortunately by this time I’m too invested in React to go back to Blaze, but in case anyone wants to carry it on, I did the beginnings of a virtual dom implementation for Blaze last year, with almost no changes to Blaze core. Would also open the way to running Blaze in a web worker, but then a solution would be needed for how best to handle template events.
12 Likes
When we talked about virtual dom internally, I thought it would be really cool if Blaze devs could easily take advantage of the big community of React components out there, and that would become easy if it were based on the same renderer. That way you could just NPM install some React component, include it in your Blaze project, and be good to go.
6 Likes
It would also make a good value proposition - “Blaze uses React” 
And Blaze lives on - LONG LIVE BLAZE!!!
1 Like
@sashko - I realize you’re talking about something else here, but I thought we could already use react in blaze
So, @miro - can’t we already say that…[quote=“miro, post:22, topic:28664”]
“Blaze uses React”
[/quote]
1 Like
Oh sure - but it’s not fully integrated into the virtual DOM pipeline so you don’t get the React performance boost.
1 Like
Oh man, that would be great - really.
A few months back, I determined that Blaze might not be making it - and for various reasons I spoke with my client for the main project I’m working on now and we decided for me to take a month or so off and learn react and then come back and refactor the whole project. I’m almost done with that (Actually, I think I’ll be back where I was by the end of today). And I have to say, I feel much more better for it. Learning any new JS technology typically makes you a better JS programmer, and I for sure feel like that’s the case with React.
HOWEVER… if I felt like Blaze was going to have a future like it might have now that we’ve made these moves back then - maybe I would have just stuck with it.
I think this will have a great impact for those who’ve learned “Meteor” and are happy with Blaze. Especially those who can’t just take a month off and pick up React. Granted, maybe I went overboard with my React training, I’d say you could probably get by with taking a week off
All and all, I feel like this is a really good thing you all have done here making blaze it’s own thing.
+1 for bringing Virtual Dom to blaze - Even though I am a React developer at heart now - I was once enjoyed Blazing it up a long time ago. And from my Blazing days, I feel like there is something Blaze still has to offer the scene.
There is something about the flexibility of Blaze/Meteor/Session on one side of things and React/Redux/Meteor on the other. For example (now, this might be wrong for several reasons - but I’m bringing it up anyways) I like how I can just import Session on the server where I have a method to insert some data into the database… And if I find that the user is not logged in - I set a Session variable which in turn triggers a “login” modal screen to request my user to login (I throw an error also right after that Session.set). I agree, that I should be checking for this on the client side - and I actually am. I just like the fact that with Session - I CAN do this from the server. And my component watching that Session variable still gets “re-rendered” because of the createContainer context - so, in effect - it’s kind of like redux, I know it’s not the same for a lot of reasons - but this way just seams simpler to me for now. And that’s what I mean - I like how with Blaze/Meteor you can just “do” what you want to do sometimes, yes I like the structure of React, it’s made me a better developer. But sometimes, freedom feels good, and get’s the job done.
2 Likes
Agreed …
What we are looking at right now is implementing Incremental DOM https://github.com/meteor/blaze/issues/45, which in theory, could be done rather quickly and produce great results. I have seen benchmarks where Virtual DOM didn’t provide that much improvement for large pages on weaker devices (due namely to the doubling of memory, you hold the page, as it seems, twice in memory)
5 Likes