←back to thread

Google is killing the open web, part 2

(wok.oblomov.eu)
418 points akagusu | 2 comments | 17 Nov 25 15:41 UTC | HN request time: 0s | 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 #
PaulHoule ◴[17 Nov 25 16:18 UTC] No.45954991[source]▶
The case for JPEG XL is much better than that for XSLT. On the other hand, people who program in C will always be a little terrified of XML and everything around it since the parsing code will be complex and vulnerable.
replies(1): >>45955226 #
1. _sr6i ◴[17 Nov 25 16:36 UTC] No.45955226[source]▶
Having a background in C/C++, that was the problem I ran into when I had to learn XSLT at translation company that used it to style documents across multiple formats. The upside of using XML was that you could store semantically rich info into the tags for the translators and designers. The downside, of course, with all the metadata, was that the files could be really large and the XSLT was usually specifically programmed for that particular document and very verbose so the XSLT template might only be used a couple times.
replies(1): >>45955399 #
2. PaulHoule ◴[17 Nov 25 16:52 UTC] No.45955399[source]▶
XSLT is really strange in that it's not really what people think it is. It's really a pattern-matching and production rules system right out of the golden age of AI but people think it is just an overcomplicated Jinja2 or handlebars.