4 ms·

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.x

by ktpsns 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 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 ago
  I guess we've both been traumatized by modern linux distros?
- leberknecht 11mo ago
  for those wondering: No, its not "d-bus hell" ^^
  - cachius 11mo ago
    It's David Bushell
- egorfine 11mo ago
  Same here. This is f..n hilarious.
- alsotang 11mo ago
  funny segmentation.
- bpoyner 11mo ago
  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.
  - Cthulhu_ 11mo ago
    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.
  - jeltz 11mo ago
    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.
  - 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 ago
    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..
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.

by ktpsns 11mo ago

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 ago
I guess we've both been traumatized by modern linux distros?
leberknecht 11mo ago
for those wondering: No, its not "d-bus hell" ^^
- cachius 11mo ago
  It's David Bushell
egorfine 11mo ago
Same here. This is f..n hilarious.
alsotang 11mo ago
funny segmentation.
bpoyner 11mo ago
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.
- Cthulhu_ 11mo ago
  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.
- jeltz 11mo ago
  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.
- 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 ago
  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..

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.