It doesn't seem like much of a charge to be led. The decision appears to have been pretty unanimous.

By browser vendors, you mean? Yes it seems like they were in agreement and many here seem to think that was largely driven by google though that's speculation.

Users and web developers seemed much less on board though[1][2], enough that Google referenced that in their announcement.

[1] https://github.com/whatwg/html/issues/11578 [2] https://github.com/whatwg/html/issues/11523

▲

akerl_ 3 hours ago | parent [-]

Yes, that's what I mean. In this comment tree, you've said:

> google has been the party leading the charge arguing for the removal.

and

> many here seem to think that was largely driven by google though that's speculation

I'm saying that I don't see any evidence that this was "driven by google". All the evidence I see is that Google, Mozilla, and Apple were all pretty immediately in agreement that removing XSLT was the move they all wanted to make.

You're telling us that we shouldn't think too hard about the fact that a Mozilla staffer opened the request for removal, and that we should notice that Google "led the charge". It would be interesting if somebody could back that up with something besides vibes, because I don't even see how there was a charge to lead. Among the groups that agreed, that agreement appears to have been quick and unanimous.

	▲	_heimdall 18 minutes ago \| parent [-]
		In the github issues I have followed, including those linked above, I primarily saw Google engineers arguing for removing XSLT from the spec. I'm not saying they are the sole architects of the spec removal, and I'm not claiming to have seen all related discussions. I am sharing my view, though, that Google engineers have been the majority share of browser engineer comments I've seen arguing for removing XSLT.