Wait - have you never said something similar? That would would rather address tech debt, or drop a feature that gets little use and has high maintance cost, so you can spend your effort on "better" things?
There's a big difference between removing something to address tech debt in an internal system, or even a normal application, and removing support for a web standard from Google Chrome.
It's the single most popular browser on the internet today, so removing support for any given standard from it means, effectively, breaking anything that uses that standard on the web. And because XSLT isn't a particularly user-visible standard, there's no easy way to tell which websites will use it, and any website that breaks because of it will just appear not to be supporting Chrome, rather than the other way around. (Flash, for instance, was a much more visible feature, and it was generally very clear when a website broke because it was using Flash when support went away. Plus, of course, it was not a web standard.)
Google isn't unilaterally removing XSLT from Chrome. They are participating in a discussion to remove it from the standards first. This would absolutely not be a Chrome-only thing, and so has nothing to do with Chrome marketshare. All the browser vendors are on board here.
