News for hackers. Stuff that matters.
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.