@trek when you use templates, you have to recreate a bunch of js language features in your template DSL @dan_abramov @kwuchu
-
-
Replying to @mjackson
@trek e.g. {{#each person in people}} could be done with a simple people.forEach(person => ...)@dan_abramov@kwuchu3 replies 0 retweets 0 likes -
Replying to @mjackson
@trek so although value-diffing may be more performant i still prefer using js to build my virtual dom structures@dan_abramov@kwuchu2 replies 0 retweets 1 like -
Replying to @mjackson
@trek there's just a lot less to learn/teach, and a whole lot less documentation to write@dan_abramov@kwuchu3 replies 0 retweets 0 likes -
Replying to @mjackson
@mjackson@dan_abramov@kwuchu templates protect from arbitrary logic in your views.1 reply 0 retweets 2 likes -
Replying to @trek
@trek we should probably just agree to disagree here. i wrote mustache.js. i'm familiar with the "logicless template"@dan_abramov@kwuchu2 replies 0 retweets 7 likes -
Replying to @mjackson
@trek i'd rather have the freedom to use js than to be forced to learn a template DSL. i can take it to my next job too@dan_abramov@kwuchu1 reply 0 retweets 0 likes -
Replying to @mjackson
@mjackson@dan_abramov@kwuchu I'd rather not inherit a project from someone who didn't know how not to abuse that freedom.1 reply 0 retweets 2 likes -
Replying to @trek
@trek@mjackson@dan_abramov@kwuchu why am i not surprised this turned into an aggro ember vs react debate4 replies 1 retweet 10 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 