News for hackers. Stuff that matters.
Re:Chrome intends to remove XSLT from the HTML spec by codedokode on Tuesday August 19, 2025 @12:50PM (#44953592)
> I've been looking at it as a secret weapon: I've been using it for the last twenty years because it's faster than everything else.

Serving a server-generated HTML page could be even faster.

Re:Chrome intends to remove XSLT from the HTML spec by ArchOversight on Tuesday August 19, 2025 @03:04PM (#44955064)
That assumes the server has a lot of additional CPU power to serve the content as HTML (and thus do the templating server side), whereas with XSLT I can serve XML and the XSLT and the client side can render the page according to the XSLT.

The XSLT can also be served once, and then cached for a very long time period, and the XML can be very small.

Re:Chrome intends to remove XSLT from the HTML spec by codedokode on Tuesday August 19, 2025 @04:22PM (#44955904)
With server-side rendering you control the amount of compute you are providing, with client-side rendering you cannot control anything and if the app would be dog slow on some devices you can't do anything.
Re:Chrome intends to remove XSLT from the HTML spec by geocar on Tuesday August 19, 2025 @12:58PM (#44953672)
> Serving a server-generated HTML page could be even faster.

Except it isn't.

Lots of things could be faster than they are.

Re:Chrome intends to remove XSLT from the HTML spec by codedokode on Tuesday August 19, 2025 @04:24PM (#44955920)
Loading one page is probably faster that loading a template and only after that loading the data with the second request, given that the network latency can be pretty high. That's why Google serves (served?) its main page as a single file and not as multiple HTML/CSS/JS files.
Re:Chrome intends to remove XSLT from the HTML spec by geocar on Tuesday August 19, 2025 @05:50PM (#44956591)
> Loading one page is probably faster that loading a template and only after that loading the data with the second request, given that the network latency can be pretty high

XSLT is XML: It can be served with the XML as a single request.

You don't have any idea what you're talking about.

> That's why Google serves (served?) its main page as a single file and not as multiple HTML/CSS/JS files.

Google.com used to be about a kilobyte. Now it's 100kb. I think it's absolutely clear Google either doesn't have the first idea how to make things fast, or doesn't care.

Re:Chrome intends to remove XSLT from the HTML spec by timeon on Tuesday August 19, 2025 @01:58PM (#44954341)
Maybe but PR author, who created the Issue there as well, gave example: 'JSON+React'. 'React' one of the slowest framework out there. Performance is rarely considered in contemporary front-end.