Thanks for the responses. @arunoda -- I've used half a dozen templating engines, and have already made my choice. I was simply questioning why lately Jade is not only the most often recommended choice, but seems to be the only recommendation. I have to assume it is because people recommend what they know, and it is the most popular. And everyone else doesn't care enough to chime in.
@martin -- I used to agree with you. For about a year, I used jade, stylus, and coffeescript. They aren't my tools of choice any longer, but I recognize the appeal. Unfortunately, it really only works if your entire team is on-board with these tools and there are rarely any staffing changes. Otherwise, in my experience, productivity suffers as new team members come up to speed with the new tools. Instead, we stick with HTML since everyone knows it and I use the Emmet [1] sublime plugin [2] to make typing it much faster. We use LESS because it is syntactically compatible with CSS and because twitter bootstrap uses it. And we use plain JS, but still have some legacy coffeescript that we tolerate. @peter -- Sounds like we are on the same page. I too prefer logic-less templating, and have gone that route for the last year or so. I tried out a completely logic-less engine called Plates [3], but it was far too buggy at the time. I haven't used transparency [4] yet, but it appears very similar to plates. Unfortunately, I doubt I would use it since it requires a DOM, which makes it less usable server-side. In the end, I chose to use Handlebars [5] since it is popular and well supported, and I avoid using it in ways that add any sort of branching or other logic into the template itself. It works well with Express, is easy to integrate into Backbone, and is the default engine with Ember, so it meets all my BE and FE needs. [1] http://docs.emmet.io/ [2] https://github.com/sergeche/emmet-sublime [3] https://github.com/flatiron/plates [4] https://github.com/leonidas/transparency [5] http://handlebarsjs.com/ On Wed, Apr 3, 2013 at 7:05 AM, Peter Rust <[email protected]> wrote: > Jade does seem to be the most popular on npm, with 235k downloads in the > last month, but it's not a landslide (handlebars has 74k, EJS has 59k, and > there are *four pages* of packages with the keyword "template"). > > > Is everyone burnt out arguing over template engines? >> > I suspect so. Since your choice of template engine doesn't usually affect > interoperability with other modules (unlike the single-callbacks vs > promises debate), you can just pick what you like best. > > Personally, I dislike Jade for the same reason Martin likes it (Jade is to > HTML what Coffeescript is to Javascript) and prefer logic-less > micro-templating that strictly does interpolation and nesting of other > templates. > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
