News for hackers. Stuff that matters.
Re:Chrome intends to remove XSLT from the HTML spec by dehrmann on Tuesday August 19, 2025 @12:16PM (#44953265)
> 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.

Re:Chrome intends to remove XSLT from the HTML spec by codedokode on Tuesday August 19, 2025 @12:26PM (#44953359)
Adding 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.
Re:Chrome intends to remove XSLT from the HTML spec by joquarky on Tuesday August 19, 2025 @03:31PM (#44955368)
Knockout.js may be off the radar these days, but has robust handling for this.

Still the best framework I've ever worked with.

Re:Chrome intends to remove XSLT from the HTML spec by codedokode on Tuesday August 19, 2025 @04:32PM (#44955987)
The 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.
Re:Chrome intends to remove XSLT from the HTML spec by troupo on Wednesday August 20, 2025 @01:54AM (#44959025)
> 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