This is a killer feature! If you are a Meteor developer / user / enthusiast register on the map
Meteor 0.8.0: Introducing the Blaze templating engine
41–50 of 50 posts
Re: Meteor 0.8.0: Introducing the Blaze templating engine
#42I've been working on a project that uses React with Meteor. One advantage that React has is that it's very easy to render the html on the server side. Once on the client React only updates this html if and when it needs to. Can Blaze do this? If not, are there plans to support it in the future?
Re: Meteor 0.8.0: Introducing the Blaze templating engine
#43I've been working on a project that uses React with Meteor. One advantage that React has is that it's very easy to render the html on the server side. Once on the client React only updates this html if and when it needs to. Can Blaze do this? If not, are there plans to support it in the future?
But for now you have to adopt a NodeJS to get this benefit, right?
Re: Meteor 0.8.0: Introducing the Blaze templating engine
#44I've been working on a project that uses React with Meteor. One advantage that React has is that it's very easy to render the html on the server side. Once on the client React only updates this html if and when it needs to. Can Blaze do this? If not, are there plans to support it in the future?
But for now you have to adopt a NodeJS to get this benefit, right?
You understand the Meteor execution model, yes? (Hint: You're already running on NodeJS)
Re: Meteor 0.8.0: Introducing the Blaze templating engine
#45They seem to be parsing the structure rather than just gluing strings, kudos for that!
However, the tricky case they've run into:
{{#if bold}}
Hello {{name}}!
{{else}}
Hello {{name}}!
{{/if}}
Hello {{name}}!
Re: Meteor 0.8.0: Introducing the Blaze templating engine
#46Earlier quoted context omitted.
If you use `shouldComponentUpdate`, then React outperforms Blaze on the circle benchmark for both single and large number of updates. See Andrey Popp JSFiddles: https://groups.google.com/forum/#!topic/meteor-core/-px_AGhj... React by default is fairly fast but what makes it stand out is that it gives the tools to make the bottlenecks faster without having to drop the nice abstraction.
Popp's fiddles don't use shouldComponentUpdate, as far as I can tell. They replace using props (application state) by components-local state and an animation prop. I'm not entirely certain that his semantics map to the original ones (in terms of expectations).
My bad :x JSFiddle is unusable on mobile and I assumed it was using shouldComponentUpdate. Anyway, the conclusion still holds, you can refactor your code to be performant while keeping in the React paradigm.
You have a lot less control over the performance of your app with data binding.
Re: Meteor 0.8.0: Introducing the Blaze templating engine
#47Earlier quoted context omitted.
But for now you have to adopt a NodeJS to get this benefit, right?
You understand the Meteor execution model, yes? (Hint: You're already running on NodeJS)
I was thinking about React. Pardon me for not knowing that Meteor had a single implementation.
Re: Meteor 0.8.0: Introducing the Blaze templating engine
#48I've been working on a project that uses React with Meteor. One advantage that React has is that it's very easy to render the html on the server side. Once on the client React only updates this html if and when it needs to. Can Blaze do this? If not, are there plans to support it in the future?
Blaze will support server-side rendering.
Re: Meteor 0.8.0: Introducing the Blaze templating engine
#49Earlier quoted context omitted.
The app I want to build would be data driven. I want it to be as fast as possible (it will have to plot graphs) and I thought I made a good choice with my current stack. The big difficulty is understanding where each library/framework shines, how to couple it with the others and when two frameworks have some overlapping functionality, which one to keep. The reason I didn't go with Meteor at first was that I didn't re…
Unless you're going to be wildly successful the moment you launch, you're better off picking one stack that you understand, creating a working version, then iterating to improve on it. If you try to do it perfectly or make it as fast as possible from the start you may never finish - and you'll never be able to test your idea.
but on other side, Meteor itself just for quick prototyping, it's quite easy to learn
Re: Meteor 0.8.0: Introducing the Blaze templating engine
#50I've been using Meteor since this past September. Great to see there's only 1 more update prior to 1.0.
Now that I've had time to check out the update in depth, I can say that this update actually affects my project in a huge way. It'll require refactoring probably around 500 of lines of code because of the elimination of {{#isolate}, {{#constant}} and preserve-inputs, and the new template.rendered functionality.