5 ms·
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"?>
by koito17 11mo ago
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>
- ktpsns 11mo agoThis is actually a clever way to distinguish if the browser supports XSLT or not. Actual content is XHTML in https://xslt.rip/index.xsl https://xslt.rip/index.xsl The author is frontend designer and has a nice website, too: https://dbushell.com/ https://dbushell.com/ I like the personal, individual style of both pages.
- konimex 11mo ago> https://dbushell.com https://dbushell.com Heh, I honestly thought the domain name stood for "D-Bus Hell" and not their own name.
- andrelaszlo 11mo agoI guess we've both been traumatized by modern linux distros?
- leberknecht 11mo agofor those wondering: No, its not "d-bus hell" ^^
- cachius 11mo agoIt's David Bushell
- egorfine 11mo agoSame here. This is f..n hilarious.
- alsotang 11mo agofunny segmentation.
- bpoyner 11mo agoChuckling 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.
- Cthulhu_ 11mo agoWhich 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.
- jeltz 11mo agoOne 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.
- rekabis 11mo ago> 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.
- tracker1 11mo agoI 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..
- qrios 11mo ago> 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 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.
- shiomiru 11mo agoIronically, 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).
- StilesCrisis 11mo agoThe page works fine in Mobile Safari.
- auscompgeek 11mo agoFirefox haven't removed XSLT support yet.
- shiomiru 11mo agoI 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.
- ahoka 11mo agoIt’s a joke.
- shevy-java 11mo agoThe 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.
- mimasama 11mo agoPale Moon still has XSLT support and has no plans to remove it: https://outerheaven.club/notice/AxFlFCfzzgRRpvubVw https://outerheaven.club/notice/AxFlFCfzzgRRpvubVw
- 11mo ago
- blablabla123 11mo agoTo 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"
- api 11mo agoI 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.
- varjag 11mo agoWe can only thank the millennials for killing the whole XML tech stack for good. That and blood diamonds industry.
- data-ottawa 11mo agoSome 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.