4 ms·
> Why should the browser contain a specific template engine, like XSLT, and not Jinja for example? Historic reasons, and it sounds like they want it to contain
by dehrmann 1y ago
> Why should the browser contain a specific template engine, like XSLT, and not Jinja for example?
Historic reasons, and it sounds like they want it to contain zero template engines. You could transpile a subset of Jinja or Mustache to XSLT, but no one seems to do it or care.
- codedokode 1y agoAdding XSLT support is as absurd as adding React into a browser (especially given that it's change detection is inefficient and requires lot of computation). Instead, browsers should provide better change tracking methods for JS objects.
- joquarky 1y agoKnockout.js may be off the radar these days, but has robust handling for this. Still the best framework I've ever worked with.
- codedokode 1y agoThe downside of knockout was that it used proxies for change tracking, and you had to create those proxies manually, so you cannot have an object with a Number property, you had to have an object with a proxy function as a property.
- troupo 1y ago> and it sounds like they want it to contain zero template engines. The funny thing? No, they want to create a new one: https://github.com/WICG/webcomponents/issues/1069 https://github.com/WICG/webcomponents/issues/1069