Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Meteor 0.8.0: Introducing the Blaze templating engine

meteor.com

Post reply on HN
Print view View original

21–30 of 50 posts

Re: Meteor 0.8.0: Introducing the Blaze templating engine

#21

Post by avital »

cookrn wrote: post #18

I took some time to read through the architecture document[0] on HTMLbars yesterday and parts of the Blaze description sound very familiar. As a general observation, both libraries are focused on outputting DOM rather than HTML strings, which is interesting for various reasons. Maybe I'm missing some of the history here re: interaction between Meteor & Tilde, but I wonder if HTMLbars could have been useful in buildin…

Hi, I work on Blaze.

HTMLBars is an excellent project and indeed does share many design principles with Blaze. They also differ in a few ways. For example, HTMLBars plans to never support full inline expressions in templates, whereas that is an explicit future goal for Blaze. So even though parts of HTMLBars could have been used in Blaze, it wouldn't give us the flexibility needed to take Blaze in the direction we think is best for our users.

[edit: Also, Blaze is shipped. :)]

Re: Meteor 0.8.0: Introducing the Blaze templating engine

#22

Post by mcrider »

xiaoma wrote: post #11
malokai wrote: post #8

I've been using Meteor since this past September. Great to see there's only 1 more update prior to 1.0.

What happens in 1.0? Is it primarily the marketing buzz you're looking forward to, or is there a specific feature?

I'm looking forward to a more stable API. I think a lot of things are solidified by this 0.8.0 release, but working up to it I've had to deal with a lot of upstream changes that forced me to refactor a lot of code. Of course, its all in the name of progress and the Meteor community is super helpful and friendly, so no big whoop.

Re: Meteor 0.8.0: Introducing the Blaze templating engine

#23

Post by chm »

I want to write a web app, an SPA. After many years of not caring about web design [1], getting back into the game is very difficult, even if my programming skills are more than 10x what they were back then.

I'm sold on JS, as to me PHP is very ugly and incomprehensible. My stack currently looks like this:

Node -> Express+Passport+Mongoose -> Bootstrap + Angular/Polymer + D3

I've only begun my project three weeks ago, but I would have hoped to have a prototype by now. Admittedly, I'm not working on this 40hrs a week, but still. I find it very hard to understand how everything fits together.

And then news like this appear, once or twice a week, which make me spend some hours reading on this or that new framework and how better it performs.

[1] I did some flash, html and js about 6-7 years ago. Also learned enough php to be disgusted by it.

Re: Meteor 0.8.0: Introducing the Blaze templating engine

#24

Post by maxharris »

xiaoma wrote: post #11
malokai wrote: post #8

I've been using Meteor since this past September. Great to see there's only 1 more update prior to 1.0.

What happens in 1.0? Is it primarily the marketing buzz you're looking forward to, or is there a specific feature?

I'm looking forward to each template having its own local reactive state so that I can get away from storing everything in session variables, which are global.

Without this feature, it's hard (or harder than it should be) to create reusable user interface code.

Re: Meteor 0.8.0: Introducing the Blaze templating engine

#25

Post by TylerE »

avital wrote: post #20
RaphiePS wrote: post #9

Can anyone speak to the difference in approach between Blaze and React? Or are they doing essentially the same thing? At first glance, this seems much better in terms of programmer productivity, given that it uses logicless templates rather than embedding HTML inside JS code. But I'd be curious if it's less performant.

Hi, I work on Blaze. React and Blaze both compile templates or components into an intermediate representation for their HTML structure (React's JSDOM; Blaze's HTMLJS). A lot of the difference in how they decide what DOM changes are necessary. React re-renders components when data changes and diffs the resulting JSDOM. The diff algorithm is fast and has simple hooks to make it faster by letting you compare state and c…

I have to say I'm pretty excited, since it now looks like there is a non-hacky way to use jade templates, which as far as I'm concerned are a big win. Any more details to shed on that aspect?

Re: Meteor 0.8.0: Introducing the Blaze templating engine

#26

Post by TylerE »

xiaoma wrote: post #11
malokai wrote: post #8

I've been using Meteor since this past September. Great to see there's only 1 more update prior to 1.0.

What happens in 1.0? Is it primarily the marketing buzz you're looking forward to, or is there a specific feature?

More the just marketing buzz, imo. I know the IntelliJ guys have said they will build in first-class Meteor support once it hits 1.0.

Re: Meteor 0.8.0: Introducing the Blaze templating engine

#27

Post by Void_ »

chm wrote: post #23

I want to write a web app, an SPA. After many years of not caring about web design [1], getting back into the game is very difficult, even if my programming skills are more than 10x what they were back then. I'm sold on JS, as to me PHP is very ugly and incomprehensible. My stack currently looks like this: Node -> Express+Passport+Mongoose -> Bootstrap + Angular/Polymer + D3 I've only begun my project three weeks ago…

Well maybe it would be worth trying Meteor for you.

I've tried something similar, that is Rails + Ember.js, and I find using Meteor.js easier.

Re: Meteor 0.8.0: Introducing the Blaze templating engine

#28

Post by rtfeldman »

avital wrote: post #20
RaphiePS wrote: post #9

Can anyone speak to the difference in approach between Blaze and React? Or are they doing essentially the same thing? At first glance, this seems much better in terms of programmer productivity, given that it uses logicless templates rather than embedding HTML inside JS code. But I'd be curious if it's less performant.

Hi, I work on Blaze. React and Blaze both compile templates or components into an intermediate representation for their HTML structure (React's JSDOM; Blaze's HTMLJS). A lot of the difference in how they decide what DOM changes are necessary. React re-renders components when data changes and diffs the resulting JSDOM. The diff algorithm is fast and has simple hooks to make it faster by letting you compare state and c…

Not to detract from the positivity of sweet new tech, but it's worth noting that "React outperforms Blaze when many elements change and Blaze outperforms React when few elements change" is the same as "React outperforms Blaze in cases where the user is capable of noticing a performance difference", which reduces to "React outperforms Blaze."

Nevertheless, seriously appreciate the detailed and informative response. :)

Re: Meteor 0.8.0: Introducing the Blaze templating engine

#29

Post by imslavko »

rtfeldman wrote: post #28
avital wrote: post #20

Earlier quoted context omitted.

Hi, I work on Blaze. React and Blaze both compile templates or components into an intermediate representation for their HTML structure (React's JSDOM; Blaze's HTMLJS). A lot of the difference in how they decide what DOM changes are necessary. React re-renders components when data changes and diffs the resulting JSDOM. The diff algorithm is fast and has simple hooks to make it faster by letting you compare state and c…

Not to detract from the positivity of sweet new tech, but it's worth noting that "React outperforms Blaze when many elements change and Blaze outperforms React when few elements change" is the same as "React outperforms Blaze in cases where the user is capable of noticing a performance difference", which reduces to "React outperforms Blaze." Nevertheless, seriously appreciate the detailed and informative response. :)

Does it mean that, theoretically, Blaze will still outperform React on a long series of small quick updates conducted by a lot of disconnected events?

Re: Meteor 0.8.0: Introducing the Blaze templating engine

#30

Post by kawera »

chm wrote: post #23

I want to write a web app, an SPA. After many years of not caring about web design [1], getting back into the game is very difficult, even if my programming skills are more than 10x what they were back then. I'm sold on JS, as to me PHP is very ugly and incomprehensible. My stack currently looks like this: Node -> Express+Passport+Mongoose -> Bootstrap + Angular/Polymer + D3 I've only begun my project three weeks ago…

Have you looked at Twitter Flight?[1][2]. Quite easy to grasp.

[1] http://flightjs.github.io

[2] https://speakerdeck.com/anguscroll/cal

Post reply on HN