Live data from Hacker News

Javascript Templating Engine Chooser

garann.github.io

21–30 of 33 posts

Re: Javascript Templating Engine Chooser

#21
post #19

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

Knockout is an MVVM (MV*) framework, it is much more than a templating engine. If it had a standalone templating module, then that module could qualify for the comparison for sure, but as it stands it would not make much sense to include it in the comparison.

Re: Javascript Templating Engine Chooser

#22
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.

Also, if you're using a tool that was built more than a year ago, you risk ridicule. Definitely a lot more work figuring out what the hottest new tools are than in traditional or backend development.

Re: Javascript Templating Engine Chooser

#24

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.

If I don't know exactly what parameters I need it's easier to quickly scan a table than toggle individual options.

Maybe I want some subset of features that aren't available together but I'm willing to compromise on one or more of them.

Re: Javascript Templating Engine Chooser

#25

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

Send in a pull request! It's on GitHub. That's what I did [0]

[0] https://github.com/garann/template-chooser/pull/20

Re: Javascript Templating Engine Chooser

#27
post #9

Is there a way to deselect an option without reloading the page? For example: Under "DOM Structure", once you select "DOM" or "String", you can never go back to seeing all the template options.

It seems a little buggy. There seem to be several state combinations that cause it to lock up.

Re: Javascript Templating Engine Chooser

#28
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.

It's the ciiiiircle of life. We're at the "Cambrian Explosion" stage of front-end frameworks. The variance in approaches, technologies, and boundaries between the various moving parts is just the ecosystem sorting itself out.

Come back in 3 years. It'll have settled down.

Re: Javascript Templating Engine Chooser

#29
post #3

It's missing DustJS, which is IMO a strong contender that does well in benchmarks http://linkedin.github.io/dustjs/ * Works in the browser and on the server * Pretty fast * logic-less but with a helpers API for when you need more power * pre-compiles templates * has template partials

I am curious why this isn't ported to more languages like mustache is. I ported it to PHP, but it's not really language specific for just the templating part, though context assignment and callbacks might be (but aren't hard).
Post reply on HN