←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.001s | source
Show context
nwellnhof ◴[17 Nov 25 16:33 UTC] 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 ◴[17 Nov 25 16:37 UTC] 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 #
granzymes ◴[17 Nov 25 16:47 UTC] No.45955346[source]▶
The standards body is deprecating XSLT with support from Mozilla and Safari (Mozilla first proposed the removal).

Not sure how you got from that to “Google is ignoring standards”.

replies(5): >>45955574 #>>45955964 #>>45955987 #>>45957993 #>>45965422 #
1. lenkite ◴[18 Nov 25 13:19 UTC] No.45965422[source]▶
> The standards body is deprecating XSLT

The "CORPO CARTEL body" is deprecating XSLT. WhatWG is a not really a standards body like the W3C.