Simon

This is going to completely break many of my websites, which use XML to provide data in a very compact format and then static XSLT 1.0 to render it as HTML.

It's extremely useful on microcontrollers because the XSLT can be provided as an immutable resource that will be cached and doesn't need to be retrieved again.

https://social.cryptography.dog/@ansuz/115031292965461771

ansuz / ऐरन (@[email protected])

chrome developers: we are thinking of dropping support for rendering RSS feeds as something other than garbage code. does anyone have any reasons not to do this? developers from many different backgrounds: yes, I rely on normal people being able to understand RSS for my business. dropping support will be disastrous for me because I can't rely on people to have some random extension installed. chrome devs: OK well we're probably going to do it anyway because we can't be bothered to support web standards. uwu google is only a teensy wee company uwu https://github.com/whatwg/html/issues/11523 #xslt #standards #openWeb

social.cryptography.dog
Aug 16, 2025 at 11:47amTusky
Show threadSimonAug 16, 2025
Presumably, the next thing they'll do is limit the alternatives to HTTPS only, which is also hard to do on a microcontroller. It's already really annoying that I can't use Brotli compression when my content can be represented by the Brotli dictionary.