←back to thread

418 points akagusu | 1 comments | | HN request time: 0.592s | source
Show context
nwellnhof ◴[] No.45955183[source]
Removing XSLT from browsers was long overdue and I'm saying that as ex-maintainer of libxslt who probably triggered (not caused) this removal. What's more interesting is that Chromium plans to switch to a Rust-based XML parser. Currently, they seem to favor xml-rs which only implements a subset of XML. So apparently, Google is willing to remove standards-compliant XML support as well. This is a lot more concerning.
replies(11): >>45955239 #>>45955425 #>>45955442 #>>45955667 #>>45955747 #>>45955961 #>>45956057 #>>45957011 #>>45957170 #>>45957880 #>>45977574 #
xmcp123 ◴[] No.45955239[source]
It’s interesting to see the casual slide of Google towards almost internet explorer 5.1 style behavior, where standards can just be ignored “because market share”.

Having flashbacks of “<!--[if IE 6]> <script src="fix-ie6.js"></script> <![endif]-->”

replies(4): >>45955346 #>>45955370 #>>45955787 #>>45956032 #
Aurornis ◴[] No.45955370[source]
I don’t get the comparison. The XSLT deprecation has support beyond Google.
replies(1): >>45956044 #
amarant ◴[] No.45956044[source]
It's just ill-informed ideological thinking. People see Google doing anything and automatically assume it's a bad thing and that it's only happening because Google are evil.

HN has historically been relatively free of such dogma, but it seems times are changing, even here

replies(4): >>45956343 #>>45956372 #>>45958522 #>>45959017 #
1. troupo ◴[] No.45959017[source]
Safari is "cautiously supportive", waiting for someone else to remove support.

Google does lead the charge on it, immediately having a PR to remove it from Chromium and stating intent to remove even though the guy pushing it didn't even know about XSLT uses before he even opened either of them.

XSLT is a symptom of how browser vendors approach the web these days. And yes, Google are the worst of them.