Chrome and Edge are removing XSLT: what breaks and what does not
What would be a modern equivalent of a JSON to HTML transformer?
That doesn't sound like a hard thing to fix? JS already comes with a ton of APIs and “web technologies”, but creating an XML equivalent to JSON.parse/JSON.stringify is somehow outside the realm of the thinkable?
and yet a single newline in a text field will shatter its validity or force you to enter escaping-hell.
(I tamed that entire general problem by making https://github.com/pmarreck/printable_binary, and it will permit you to pack all binary data into a string, without any escaping issues, while retaining ascii legibility, although that requires a decoding step.)
So would a single & or > in the body of an XML element, you know.
For example: base64 API, audio nodes API, canvas API, encryption etc.
And XSLT can be implemented this way as well.
What you repeat, it's Google marketing bullshit of the only thing with which they could compete - JS engine.
Want to make browsers easier ? - removing JavaSript and *fixing browser bugs instead* ('outsourced' to the user) will do that better.
BTW JavaSript it's not W3 standard, XSLT is.
("Live and let live", "Don't break the Web" - "breaking web pages that were made 20 years ago is unlikely to result in bug reports")
Google can do literally nothing to disrupt RSS since its only important use is in real feed readers, which Chrome isn't.
Surely free-tier ChatGPT can in 5 minutes make a replacement that you could use to parse an RSS feed and render whatever you want. I guess it wouldn't be at the exact feed URL, though the server could use User-Agent to cheat at that, probably.