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