When, Oh When, Mustache 2.0?

[trans]

Is there any hope Mustache 2.0 will make a break for it within the year?

If there is a hold up b/c of so many feature possibilities and undecided choices to make about them, may I suggest that this process be divided into 2.0 and a 3.0 tracks?

For 2.0 just adopt the things you are sure about and/or already have precedence in the field. For instance Hogan.js has already adopted template inheritance. I recommend taking that, adjusting it so the notation is more intuitive/useful (for instance, my recommendation), and go with it. Another possibility is Handlebar.js style helpers. And personally I'd like to see Liquid style filters. But I digress. The point is pick the things that are ready or near ready to go, and make 2.0 out of those and save anything that is still well up in the air for 3.0.

Personally I feel there is some urgency to get the move on, as new template engines are making the scene to draw people away from a common standard, which Mustache has succeeded in doing more than any other for logicless templates.

[spullara]

Template inheritance solves many of the issues with mustache in real world applications in a declarative way and is still my #1 feature request for the specification. There are now several implementations that support it in various languages including hogan.js, mustache.java and phly_mustache.

[janl]

As a matter of principle, I don't think a spec should ever lead development. We need to get one or two implementations out (say JS and Ruby e.g.) that could pioneer what a "2.0" mustache could look like and then we can glue it into the spec.

[trans]

@janl However there are already implementations in the field for certain features, such as template inheritance in Hogan.js. So this already partially accomplished.

[jgonggrijp]

I'm closing this, partly because the discussion is long dead but mostly because having any particular version released should not be a goal in itself.