· javascript

Death comes for XSLT

Subscribe Blog RSS feed Notes RSS feed or Combined RSS feed and follow Mastodon Bluesky Last halloween, Google decided to kill XSLT.


That was not a unilateral decision mind you, Google said “jump” and other browser vendors said “how high?” In response, I published my Intent to Deprecate and Remove Google Chrome. A performative declaration of course, I don’t install spyware.

Fearing my parody lacked seriousness, I created XSLT.RIP to ensure the developer world was informed of Google’s death note. This did the trick, although a few commenters believed it was satire. The website itself is built with XSLT and when Google kills XSLT they’ll kill my website.

The web standards process and its stewards (Big Browser) used to adhere to a social contract. Backwards compatibility was a major design principle. Under no circumstances do you ever purposefully break the web.

Google decided to renege and break the web. XSLT.RIP will be broken soon and I’ll sit back and watch Google break it.

Earlier coverage

Related coverage

Also worth reading

  1. TypeScript scode-typescript/v1.0.2 released, bundling TypeScript 7.0.2
  2. angular 22.3.0-next.4 released
  3. Gas Town Builder: All AI Software Factories Are Bespoke
  4. HUMAN Security's Lindsay Kaye discusses AI-generated malware traits, patching time, and fraud scaling
  5. Gartner report shows AI risks dominate top five enterprise concerns