Google is killing the open web, part 2

The author criticizes Google's decision to deprecate XSLT support in browsers, arguing it's an intentional move to harm the open web. Instead of fixing security flaws in the XSLT library, Google is offering a JavaScript polyfill that requires users to change their implementations, potentially leading to increased developer effort and a less robust solution. This is compared to past actions by Mozilla, also under pressure, to remove RSS features without adequate replacements. The author urges users not to comply with these changes, to report broken functionality, and to continue using XSLT. The article also touches upon the WHATWG's perceived shift towards corporate interests over open web principles, the potential for a "user versus corporations" browser war, and the decline of plugin flexibility in favor of controlled extensions. It suggests that the web's current direction sacrifices user control and privacy for corporate gain, lamenting the loss of flexibility and the "enshittification" of the web.