I believe Chrome uses libxml2 (though perhaps they use libexpat too) and the WHATWG has claimed that XSLT should not exist as a part of the HTML spec (it should and does), so the WHATWG Google members can force Javascript rendering on everyone and secure their advertising monopoly (which is loaded through js). Their claim is that libxml2 is too security riddled and they can’t contribute any work to it even though they have plenty of people and money to help fix it and they just wrote a post claiming that LLMs has helped reduce the amount of bugs in Chrome. The jerks even used LLMs to generate an untested polyfill in Javascript so that they can reduce the absolutely stellar performance of XML rendering to slow Javascript. They also used the untested pollyfill as a reason to remove it.
These are people who supposedly like the diverse web and performant technologies.
alt Hacker News
I believe Chrome uses libxml2 (though perhaps they use libexpat too) and the WHATWG has claimed that XSLT should not exist as a part of the HTML spec (it should and does), so the WHATWG Google members can force Javascript rendering on everyone and secure their advertising monopoly (which is loaded through js). Their claim is that libxml2 is too security riddled and they can’t contribute any work to it even though they have plenty of people and money to help fix it and they just wrote a post claiming that LLMs has helped reduce the amount of bugs in Chrome. The jerks even used LLMs to generate an untested polyfill in Javascript so that they can reduce the absolutely stellar performance of XML rendering to slow Javascript. They also used the untested pollyfill as a reason to remove it.
These are people who supposedly like the diverse web and performant technologies.