Despite rather heated discussion just three weeks they started just two weeks prior https://github.com/whatwg/html/issues/11523
[deleted]
"Remove mentions of XSLT from the html spec"
11–20 of 559 posts
Re: "Remove mentions of XSLT from the html spec"
#12having browsers transform XML data into HTML via XSLT is a cool feature, and it works completely statically, without any server-side or client-side code. Would be a shame if that was removed. I have a couple dozen XML databases that I made accessible in a browser using xslt...
Re: "Remove mentions of XSLT from the html spec"
#13I love how one company can do whatever they want. This is perfect.
How do you think we got into this mess in the first place? First it was Netscape, then Microsoft, now Google.
Re: "Remove mentions of XSLT from the html spec"
#14Re: "Remove mentions of XSLT from the html spec"
#15Previously:
Should we remove XSLT from the web platform? – 4 days ago (89 comments):
https://news.ycombinator.com/item?id=44909599
XSLT – Native, zero-config build system for the Web – 27th June 2025 (328 comments):
Re: "Remove mentions of XSLT from the html spec"
#16I love how one company can do whatever they want. This is perfect.
“Free markets and capitalism”. They give us superior, user centered, transparent products.
Re: "Remove mentions of XSLT from the html spec"
#17Despite rather heated discussion just three weeks they started just two weeks prior https://github.com/whatwg/html/issues/11523
It’s another “we listened the community and nobody told us no” moment. Like Go’s telemetry issue. Google is boneheaded and hostile to open web at this point, explicitly.
> It’s another “we listened the community and nobody told us no” moment. Like Go’s telemetry issue.
Go changed their telemetry to opt-in based on community feedback, so I'm not sure what point you're trying to make with that example.
Re: "Remove mentions of XSLT from the html spec"
#18The idea of building something like PDF.js makes a lot of sense. I think the core crux of it though is the polyfill should be in the browser, not something that a site maintainer has to manually implement.
Re: "Remove mentions of XSLT from the html spec"
#19> @whatwg whatwg locked as too heated and limited conversation to collaborators
Too heated? Looked pretty civil and reasonable to me. Would it be ridiculous to suggest that the tolerance for heat might depend on how commenters are aligned with respect to a particular vendor?
Re: "Remove mentions of XSLT from the html spec"
#20This proposal seems to be aimed at removing native support in favor of a WASM-based polyfill (like PDF.js, I guess) which seems reasonable?
Google definitely throws its weight around too much w.r.t. to web standards, but this doesn't seem too bad. Web specifications are huge and complex so trying to size down a little bit while maintaining support for existing sites is okay IMO.