Re:Announcing Handlebars.js (A Mustache Superset)
by judofyr on Friday September 10, 2010 @01:31AM
(#1677985)
Heh, I've already used the name Handlebars for a Mustache-related project: http://github.com/judofyr/handlebars. It's basically a JIT for Mustache which speeds up rendering. Nobody uses it, though, so I don't mind.
BTW: I've written major parts of the current Mustache implementation, do you want some help on a Ruby port?
Re:Announcing Handlebars.js (A Mustache Superset)
by grandalf on Thursday September 09, 2010 @11:59PM
(#1677842)
What's the saying again... any time you start building a template engine you'll end up inventing django templates... ?
This looks great. I love mustache and use it on one of my projects. A bit more added syntax power would be nice, but it could easily begin to violate the rule of not being code.
Re:Announcing Handlebars.js (A Mustache Superset)
by wycats on Friday September 10, 2010 @12:51AM
(#1677919)
One of my guiding principles with Handlebars was explicitly to avoid adding any new features in the template itself that were not ways to reference a part of the JS. Normal Mustache gives you one simple way to reference a key in the current context--handlebars adds an extended path syntax and a mechanism for passing a context to lambdas (which already exist in Mustache).
Re:Announcing Handlebars.js (A Mustache Superset)
by grandalf on Friday September 10, 2010 @01:58AM
(#1678026)
Interesting. I'd actually like to see Mustache go in the direction of being a bit more like django templates by adding filters, which I think are no more likely to confuse a designer than plain old mustache tags.
Re:Announcing Handlebars.js (A Mustache Superset)
by tchvil on Friday September 10, 2010 @04:05AM
(#1678222)
When I started to build "my" template engine, I took a total different route than django template. I wanted the HTML and the logic(javascript) strictly separated. The designer can build and maintain the HTML while the developer can write JS code. It is called PURE http://beebole.com/pure
BTW: I've written major parts of the current Mustache implementation, do you want some help on a Ruby port?
This looks great. I love mustache and use it on one of my projects. A bit more added syntax power would be nice, but it could easily begin to violate the rule of not being code.
Naming projects is the worst.