3 ms·
> no one wants to maintain libxslt For $0? Probably not. For $40m/year, I bet you could create an entire company that just maintains and supports all these
by themafia 1y ago
> no one wants to maintain libxslt
For $0? Probably not. For $40m/year, I bet you could create an entire company that just maintains and supports all these "abandoned" projects.
- ExoticPearTree 1y ago> or $0? Probably not. For $40m/year, I bet you could create an entire company No sane commercial entity will dump even a cent into supporting an unused technology. You have better luck pitching this idea to your senator to set up an agency for dead stuff - it will create tens or hundreds of jobs. And what's $40mm in the big picture?
- themafia 1y ago> your senator Funny you should mention that. US Title Code uses XSLT. https://simonwillison.net/2025/Aug/19/xslt/ https://simonwillison.net/2025/Aug/19/xslt/
- ExoticPearTree 1y agoI know it is there. I am more curious as to why no one updated all that to modern browser technology.
- phantasmish 1y agoUntil these recent rumblings out of Google, it was modern browser technology.
- ExoticPearTree 1y ago> Until these recent rumblings out of Google, it was modern browser technology. It is supported technology. That's all it is. And it will be no more. No one is stopping you from rendering your XML to HTML server side using XSLT.
- wpm 1y agoWhy change it? It’s only an update it if improves something.