News for hackers. Stuff that matters.
Re:XSLT RIP by koito17 on Monday November 10, 2025 @02:46AM (#45873491)
I was hoping the site itself would be an XML document. Thankfully, it is an XML document.

  % curl https://xslt.rip/
  <?xml version="1.0" encoding="UTF-8"?>
  <?xml-stylesheet href="/index.xsl" type="text/xsl"?>
  <html>
    <head>
      <title>XSLT.RIP</title>
    </head>
    <body>
      <h1>If you're reading this, XSLT was killed by Google.</h1>
      <p>Thoughts and prayers.</p>
      <p>Rest in peace.</p>
    </body>
  </html>
Re:XSLT RIP by ktpsns on Monday November 10, 2025 @03:22AM (#45873713)
This is actually a clever way to distinguish if the browser supports XSLT or not. Actual content is XHTML in https://xslt.rip/index.xsl

The author is frontend designer and has a nice website, too: https://dbushell.com/

I like the personal, individual style of both pages.

Re:XSLT RIP by konimex on Monday November 10, 2025 @03:32AM (#45873792)
> https://dbushell.com

Heh, I honestly thought the domain name stood for "D-Bus Hell" and not their own name.

Re:XSLT RIP by andrelaszlo on Monday November 10, 2025 @05:39AM (#45874584)
I guess we've both been traumatized by modern linux distros?
Re:XSLT RIP by leberknecht on Monday November 10, 2025 @05:40AM (#45874588)
for those wondering: No, its not "d-bus hell" ^^
Re:XSLT RIP by cachius on Monday November 10, 2025 @07:39AM (#45875363)
It's David Bushell
Re:XSLT RIP by egorfine on Monday November 10, 2025 @06:53AM (#45875046)
Same here. This is f..n hilarious.
Re:XSLT RIP by alsotang on Monday November 10, 2025 @07:42AM (#45875391)
funny segmentation.
Re:XSLT RIP by bpoyner on Monday November 10, 2025 @07:49AM (#45875448)
Chuckling at the disclaimer 'No AI made by a human.' I doubt many web devs could tell you that because so many use AI now. I was speaking with a web dev this summer and he told me AI made him at least twice as productive. It's an arms race to the bottom imo.
Re:XSLT RIP by Cthulhu_ on Monday November 10, 2025 @08:14AM (#45875643)
Which begs the question, are people consciously measuring their productivity? If so, how? And did they do it the same way before and after using AI tooling?

Anecdotal, but I don't measure my productivity, because it's immeasurable. I don't want to be reduced to lines of code produced or JIRA tickets completed. We don't even measure velocity, for that matter. Plus when I do end up with a task that involves writing something, my productivity depends entirely on focus, energy levels and motivation.

Re:XSLT RIP by jeltz on Monday November 10, 2025 @08:29AM (#45875803)
One of the only studied made so far showed lower actual productivity despite higher self reported productivity. That study was quite limited but I would take self reported productivity with a huge grain of salt.
Re:XSLT RIP by rekabis on Monday November 10, 2025 @02:13PM (#45879608)
> he told me AI made him at least twice as productive.

He’s not only lying to you, he’s also lying to himself.

Recent 12-month studies show that less than 2% of AI users saw an increase in work velocity, and those were only the very top-skilled workers. Projection also indicated that of the other 98%, over 90% of them will never work faster with AI than without, no matter how long they work with AI.

TL;DR: the vast majority of people will only ever be slower with AI, not faster.

Re:XSLT RIP by tracker1 on Monday November 10, 2025 @06:46PM (#45882438)
I tried Github CoPilot for about a year, I may try Claude for a bit sooner or later.

It felt like it got in the way about half the time. The only place I really liked it was for boilerplate SQL code... when I was generating schema migration files, it did pretty good at a few things based on what I was writing. Outside that, I don't feel like it helped me much.

For the Google search results stuff, Gemini, I guess... It's hit or miss... sometimes you'll get a function or few things that look like they should work, but no references to the libraries you need to install/add and even then may contain errors.

I watched a friend who is really good with the vibe coding thing, but it just seemed like a frustrating exercise in feeding it the errors/mistakes and telling it to fix them. It's like having a brilliant 10yo with ADD for a jr developer..

Re:XSLT RIP by DANmode on Monday November 10, 2025 @07:03PM (#45882554)
…that never stops asking you for more work.

And doesn’t bother you when the tab is closed.

I can see why a lot of high school and college kids are going to need to claw.

Re:XSLT RIP by tracker1 on Wednesday November 12, 2025 @11:19AM (#45902013)
The issue is that you can't give AI a task and let it go off and it actually performs said task in a couple hours and then comes to ask for more... you have to pretty much baby sit it.

Now, I could see a single person potentially managing 2-3 AI sessions across different projects as part of a larger application. Such as a UI component/section along with one or more backend pieces. But then, you're going to need 2-3x the AI resources, network use, etc. Which is something I wouldn't mind experimenting with on someone else's dime.

Re:XSLT RIP by DANmode on Wednesday November 12, 2025 @12:51PM (#45903281)
Are you using project architecture, and rules documents?
Re:XSLT RIP by qrios on Monday November 10, 2025 @10:23AM (#45876841)
> This is actually a clever way to distinguish if the browser supports XSLT or not. Actual content is XHTML in https://xslt.rip/index.xsl

I agree it is a clever way. But it also shows exactly how hard it is to use XML and XSLT in a "proper way": Formal everything is fine to do it in this way (except the server is sending 'content-type: application/xml' for the /index.xsl, it should be 'application/xslt+xml').

Almost all implementations in XML and XSLT that I have seen in my career showed a nearly complete lack of understanding of how they were intended to be used and how they should work together. Starting with completely pointless key/value XMLs (I'm looking at you, Apple and Nokia), through call-template orgies (IBM), to ‘yet-another-element-open/-close’ implementations (almost every in-house application development in PHP, JAVA or .NET).

I started using XSLT before the first specification had been published. Initially, I only used it in the browser. Years later, I was able to use XSLT to create XSDs and modify them at runtime.

Re:XSLT RIP by shiomiru on Monday November 10, 2025 @03:45AM (#45873880)
Ironically, that text is all you get if you load the site from a text browser (Lynx etc.) It doesn't feel too different from <noscript>This website requires JavaScript</noscript>...

I now wonder if XSLT is implemented by any browser that isn't controlled by Google (or derived from one that is).

Re:XSLT RIP by auscompgeek on Monday November 10, 2025 @04:01AM (#45873984)
Firefox haven't removed XSLT support yet.
Re:XSLT RIP by shiomiru on Monday November 10, 2025 @04:09AM (#45874035)
I should've worded differently. By the narrative of this website, Google is "paying" Mozilla & Apple to remove XSLT, thus they are "controlled" by Google.

I personally don't quite believe it's all that black and white, just wanted to point out that the "open web" argument is questionable even if you accept this premise.

Re:XSLT RIP by ahoka on Monday November 10, 2025 @07:02AM (#45875110)
It’s a joke.
Re:XSLT RIP by shevy-java on Monday November 10, 2025 @08:20AM (#45875705)
The problem is that the web is no longer really "open". Google kind of controls most of it right now. Just look at all the admoney influx.
Re:XSLT RIP by mimasama on Tuesday November 11, 2025 @11:06AM (#45888930)
Pale Moon still has XSLT support and has no plans to remove it: https://outerheaven.club/notice/AxFlFCfzzgRRpvubVw
Re:XSLT RIP by le-mark on Monday November 10, 2025 @04:59AM (#45874360)
> now wonder if XSLT is implemented by any browser that isn't controlled by Google (or derived from one that is).

Edge IE 11 mode is still there for you. Which also supports IE 6+ like it always did, presumably. They didn’t reimplement IE in Edge; IE is still there. Microsoft was all in on xml technologies back in the day.

Re:XSLT RIP by meindnoch on Monday November 10, 2025 @05:40AM (#45874586)
Opera.
Re:XSLT RIP by StilesCrisis on Monday November 10, 2025 @07:46AM (#45875420)
The page works fine in Mobile Safari.
Re:XSLT RIP by layer8 on Monday November 10, 2025 @12:31PM (#45878328)
I suspect that it wouldn't actually be that difficult to add XSLT support to a textmode browser, given that XSLT libraries exist and that XSLT in the browser is a straightforward application of it. They just haven't bothered with it.
Re:XSLT RIP by blablabla123 on Monday November 10, 2025 @05:28AM (#45874517)
To me XSLT came with a flood of web complexity that led to having effectively only 2 possible web browsers. It seems a bit funny because the website looks like straight out of the 90s when "everything was better"
Re:XSLT RIP by api on Monday November 10, 2025 @05:44AM (#45874613)
I have the same mixed feelings. Complexity is antidemocratic in a sense. The more complex a spec gets the fewer implementations you get and the more easily it can be controlled by a small number of players.

It’s the extend part of embrace, extend, extinguish. The extinguish part comes when smaller and independent players can’t keep up with the extend part.

A more direct way of saying it is: adopt, add complexity cost overhead, shake out competition.

Re:XSLT RIP by FredPret on Monday November 10, 2025 @08:54AM (#45876040)
This is also the argument against overregulation.

A little bit can be very good, a lot can strangle everyone but the biggest players

Re:XSLT RIP by api on Monday November 10, 2025 @08:56AM (#45876054)
Yes, it is. Complexity is a regressive tax.
Re:XSLT RIP by varjag on Monday November 10, 2025 @09:05AM (#45876131)
We can only thank the millennials for killing the whole XML tech stack for good. That and blood diamonds industry.
Re:XSLT RIP by grishka on Monday November 10, 2025 @11:22AM (#45877504)
On the web. I, among other things, make Android apps, and Android and XML are one and the same. There is no such thing as Android development without touching XML files.
Re:XSLT RIP by spixy on Monday November 10, 2025 @02:44PM (#45880016)
Flutter? React Native? Maui?
Re:XSLT RIP by grishka on Monday November 10, 2025 @05:32PM (#45881865)
None of that is what I would call "Android development".

But even if you use one of those terrible technologies, your app still needs a manifest and some native resources.

Re:XSLT RIP by varjag on Tuesday November 11, 2025 @04:06AM (#45885396)
I did Android Developer Challenge back in 2008 and honestly don't remember doing that much of XML. Although it is the technology from peak XML days so perhaps you're right.
Re:XSLT RIP by data-ottawa on Monday November 10, 2025 @09:46AM (#45876512)
Some of it deserved to die, mostly because it was misused.

I don’t know how many times I had to manually write <![CDATA[ … ]]>

I know all markup languages have their quirks, XML could be come impressively complex and inscrutable.

Re:XSLT RIP by shadowgovt on Monday November 10, 2025 @09:51AM (#45876552)
It has, I think, one nice feature that few markups I use these days have: every node is strongly-typed, which makes things like XSLT much cleaner to implement (you can tell what the intended semantics of a thing is so you aren't left guessing or hacking it in with __metadata fields).

... but the legibility and hand-maintainability was colossally painful. Having to tag-match the closing tags even though the language semantics required that the next closing tag close the current context was an awful, awful amount of (on the keyboard) typing.

Re:XSLT RIP by layer8 on Monday November 10, 2025 @12:25PM (#45878249)
It's far from dead, though. XML is deeply ingrained in many industries and stacks, and will remain so for decades to come, probably until something better than JSON comes along.
Re:XSLT RIP by varjag on Monday November 10, 2025 @02:50PM (#45880108)
Yes, kind of like COBOL. Dead.
Re:XSLT RIP by layer8 on Monday November 10, 2025 @02:59PM (#45880198)
You have no idea. New projects with XML-based formats and interfaces are being implemented all the time. XML isn’t going anywhere.
Re:XSLT RIP by varjag on Tuesday November 11, 2025 @03:56AM (#45885356)
There was fresh COBOL code written up until early 1990s too, long past its heyday.

Thing is you couldn't swing a dead cat in 00s without hitting XML. Nearly every job opening had XML listed in requirements. But since mid-2010s you can live your entire career without the need to work on anything XML-related.

Re:XSLT RIP by latexr on Tuesday November 11, 2025 @05:20AM (#45885818)
Apple’s operating systems to this day make heavy use of XML by way of plists. You can’t have an app without it.

https://en.wikipedia.org/wiki/Property_list

Re:XSLT RIP by varjag on Tuesday November 11, 2025 @05:26AM (#45885850)
I guess? Although in the few iOS/watchOS apps I made I never edited it manually.
Re:XSLT RIP by latexr on Tuesday November 11, 2025 @05:41AM (#45885930)
But it’s still there and needs to be supported by the OS and tooling. Wether you edit it manually isn’t relevant (and as counterpoint, I do it all the time, for both apps and launchd agents).
Re:XSLT RIP by varjag on Tuesday November 11, 2025 @05:51AM (#45885989)
Of course it's there. Expecting all the stuff laid in 00s disappear overnight would be unrealistic.

COBOL code is also still there.

Re:XSLT RIP by efreak on Monday November 10, 2025 @01:47PM (#45879330)
There's still epub and tons of other standards built on xml and xhtml. Ironically, the last epub file I downloaded, a comic book from humble bundle, had a 16mb css file composed entirely of duplicate definitions of the same two styles, and none of it was needed at all (set each page and image to the size of the image itself, basically)
Re:XSLT RIP by MetroWind on Tuesday November 11, 2025 @12:47PM (#45890438)
RSS, MusicXML, SVG, Docbook, Epub, JATS, XMP, ...

Sorry, web frontend is not the "whole XML tech stack", despite popular belief.

And yes all of the above are mainstream in their respective industry.

Re:XSLT RIP by mrguyorama on Monday November 10, 2025 @12:36PM (#45878401)
But this is wrong.

It was not rendering that killed other browsers. Rendering isn't the hard part. Getting most of rendering working gets you about 99% of the internet working.

The hard part, the thing that killed alternative browsers, was javascript.

React came out in 2012, and everyone was already knee-deep in earlier generation javascript frameworks by then. Shortly after, Google would release the V8 engine which was able to bring the sluggish web back to some sense of usable. Similarly, Mozilla had to spend that decade engineering their javascript engine to claw itself out of the "Firefox is slow" gutter that people insisted.

Which is funny because if you had adblock, I'm not convinced firefox was ever slow.

A modern web browser doesn't JUST need to deal with rendering complexity, which is manageable and doable.

A modern web browser has to do that AND spin up a JIT compiler engineering team to rival Google or Java's best. There's also no partial credit, as javascript is used for everything.

You can radically screw up rendering a page and it will probably still be somewhat usable to a person. If you get something wrong about javascript, the user cannot interact with most of the internet. If you get it 100% right and it's just kind of slow, it is "unusable".

Third party web browsers were still around when HTML5 was just an idea. They died when React was a necessity.

Re:XSLT RIP by MrJohz on Monday November 10, 2025 @03:22PM (#45880456)
Conveniently, all three of the major JS engines can be extracted from the browsers they are developed for, and used in other projects. Node and Bun famously use V8 and the WebKit one, and Servo I believe embeds SpiderMonkey.

If you want to start a new browser project, and you're not interested in writing a JS engine from scratch, there are three off-the-shelf options there to choose from.

Re:XSLT RIP by robocat on Wednesday November 12, 2025 @02:08AM (#45897178)
Servo and SpiderMonkey: https://github.com/servo/mozjs
Re:XSLT RIP by deafpolygon on Tuesday November 11, 2025 @04:26AM (#45885529)
This tracks - most simpler browsers run great, until anything more than basic JS is introduced. Then they slow to a crawl.