Google did not unilaterally decide to kill XSLT
meyerweb.com
Google did not unilaterally decide to kill XSLT
1–10 of 138 posts
Re: Google did not unilaterally decide to kill XSLT
#2Also: It deserved to die
Re: Google did not unilaterally decide to kill XSLT
#3[flagged]
Re: Google did not unilaterally decide to kill XSLT
#4I like how the resource issue is hand waived away because some random manager decided not to do it, and that's somehow a force of nature now.
Re: Google did not unilaterally decide to kill XSLT
#5I think one of the major problems with open source development is its hard to ever remove anything because the vocal minority who likes it will hound you. But removing things is just as, if not more important to good software as adding features.
Obligatory: https://xkcd.com/1172/
Re: Google did not unilaterally decide to kill XSLT
#6A/B testing the removal of a browser standard gives me pause. Is there precedent for that?
Re: Google did not unilaterally decide to kill XSLT
#7I like how the resource issue is hand waived away because some random manager decided not to do it, and that's somehow a force of nature now.
Well yes? People get to decide what to do with their own money, and managers get to decide what to do with the companies' money. That's basically what being a manager means in the first place. They decided spending that money on maintaining a barely used feature was not a very good use of the budget, and that it might be better spent on something that people actually use.
Re: Google did not unilaterally decide to kill XSLT
#8I like how the resource issue is hand waived away because some random manager decided not to do it, and that's somehow a force of nature now.
People who want that feature to stay in the browsers should put up some money to fund continued development and maintenance.
Re: Google did not unilaterally decide to kill XSLT
#9[flagged]
Re: Google did not unilaterally decide to kill XSLT
#10A/B testing the removal of a browser standard gives me pause. Is there precedent for that?
SameSite by default cookies come to mind: https://www.chromium.org/updates/same-site/ (and to be clear, this is a removal of functionality. The "feature" is to make cookies not work in certain contexts)
Outside of web browsers, i think X11 is somewhat famous for this sort of thing.