Wouldn't it be better if all interested parties band together and put forth a XML+XSLT-to-HTML translation with a common interface, and then integrate that?
I have lots of ideas for things that can just be removed.
We could remove framesets and remove var from javascript. Remove the Date object now that there is a Temporal api. Remove tables and flexbox now that there is grid. xhr can go too now that we have fetch. The <center> tag isn't needed anymore. I'm sure we can find support from people disliking onclick and onsomething attributes. Or how about hoisting? Surely we can simply rm that? Removing things doesn't have to be limited to older things. asm.js and web workers weren't really necessary at all.
The idea is not to just remove things for the sake of removing things, but to engage in a cost-benefit analysis. Most of the things listed above either are very widely used or don't cost much or have other downsides to maintain. By contrast, when things have been removed from the Web platform in the past, it was because they were causing problems out of proportion to the amount of breakage induced by removing them. In the case of XSLT, the problem is the attack surface that it adds.
Reading online for a bit it seems cors already ruined much of the fun. If you think about it, even with the "*" header you end up with a html document served from a different place than the url would suggest.
Kinda sad since slapping a generic template onto some familiar xml implementation seems a wonderful thing.
I've always wanted browsers to provide a set of standard templates. 90% of the time I don't care about the design, I just want something functional right now.
