Javascript Templating Engine Chooser • Hacker News Board

Re: Javascript Templating Engine Chooser

#11

Post by jdkanani » Fri, May 31, 2013, 3:58 PM UTC

No option remains for Both, logic-less and fast.

Re: Javascript Templating Engine Chooser

#12

Post by tlrobinson » Fri, May 31, 2013, 4:09 PM UTC

I'd rather just see a matrix.

Re: Javascript Templating Engine Chooser

#13

Post by jlongster » Fri, May 31, 2013, 4:11 PM UTC

It's also missing Nunjucks, which works in browser and server, can precompile templates (when done so is really fast), lets you do more logic in templates, has autoescaping, and a bunch of other stuff. Some big project like Mozilla's new Marketplace is using it.

https://github.com/jlongster/nunjucks

Re: Javascript Templating Engine Chooser

#14

Post by thezilch » Fri, May 31, 2013, 4:16 PM UTC

Missing several from LinkedIn's throwdown: http://engineering.linkedin.com/frontend/client-side-templat...

Re: Javascript Templating Engine Chooser

#15

Post by dmix » Fri, May 31, 2013, 4:23 PM UTC

Unreadable font.

Re: Javascript Templating Engine Chooser

#16

Post by wasd » Fri, May 31, 2013, 4:34 PM UTC

I encourage you who have found missing frameworks to submit a pull request instead of posting a comment.

Re: Javascript Templating Engine Chooser

#17

Post by knowtheory » Fri, May 31, 2013, 4:38 PM UTC

tlrobinson wrote: post #12

I'd rather just see a matrix.

It might be more helpful if you provided an argument that wasn't just an assertion of your personal tastes.

Re: Javascript Templating Engine Chooser

#18

Post by jtchang » Fri, May 31, 2013, 4:39 PM UTC

This is just one of the reasons why I feel developing web apps has gotten harder. While there are a lot of javascript frameworks it is likely two projects pick different routes. It basically means if I need to maintain a project I will have to learn a new javascript library.

Re: Javascript Templating Engine Chooser

#19

Post by path411 » Fri, May 31, 2013, 4:48 PM UTC

Really surprised knockoutjs isn't mentioned. It is the default templating engine in a default .NET MVC project.

Re: Javascript Templating Engine Chooser

#20

Post by nilliams » Fri, May 31, 2013, 5:19 PM UTC

jtchang wrote: post #18

This is just one of the reasons why I feel developing web apps has gotten harder. While there are a lot of javascript frameworks it is likely two projects pick different routes. It basically means if I need to maintain a project I will have to learn a new javascript library.

Hmm, I see why it could feel like that but I don't really agree. Here's another angle:

Would you rather learn some (hopefully) very well worked-out library with good documentation and all the edge-cases slaved over, with multiple contributors, with Stack Overflow questions about it ... or, would you like to learn some random guy's non-library library, because he was scared of libraries, so he just made up a load of ad-hoc conventions in his codebase.

I'd rather learn to use Backbone, Angular and Ember, than have to deal with big-ball of mud code based on no library in particular. Same goes for templating libraries, I'd rather learn a handful (after all they're relatively trivial to use), than come to a codebase that uses none at all.