←back to thread

Google is killing the open web, part 2

(wok.oblomov.eu)
418 points akagusu | 1 comments | 17 Nov 25 15:41 UTC | HN request time: 0.225s | source
Show context
andsoitis ◴[17 Nov 25 15:53 UTC] No.45954687[source]▶
I don’t know. The author makes some arguments I could get entertain and get behind, but they also enumerate the immense complexity that they want web browsers to support (incl. Gopher).

Whether or not Google deprecating XSLT is a “political” decision (in authors words), I don’t know that I know for sure, but I can imagine running the Chrome project and steering for more simplicity.

replies(5): >>45954991 #>>45955005 #>>45955021 #>>45955842 #>>45958065 #
ablob ◴[17 Nov 25 16:20 UTC] No.45955021[source]▶
"Steering for more simplicity" would be a political decision. Keeping it is also a political decision.

Removing a feature that is used, while possibly making chrome more "simple", also forces all the users of that feature to react to it, lest their efforts are lost to incompatibility. There is no way this can not be a political decision, given that either way one side will have to cope with the downsides of whatever is (or isn't) done.

PS: I don't know how much the feature is actually used, but my rationale should apply to any X where X is a feature considered to be pruned.

replies(2): >>45955117 #>>45955373 #
1. tracker1 ◴[17 Nov 25 16:50 UTC] No.45955373[source]▶
I would argue that FTP and Gopher were far more broadly used in browsers than XSLT ever was... but they still removed them. They also likely didn't present nearly the burden of support for XSLT either.