Browsers really should have embraced XSLT rather that abandoned it. Now we're stuck trying yet again to reinvent solutions already handled by REST [1].
XSLT is the solution domain specialists and philosophers. Abandoning it is the vote of the market and market interests, the wisdom of crowds at work. This is the era of scale not expertise, enjoy the fruits.
RSS.style is my site. I'm currently testing a JavaScript-based workaround that should look just like the current XSLT version. It will not require the XSLT polyfill (which sort-of works, but seems fragile).
One bonus is that it will be easier to customize for people that know JavaScript but don't know XSLT (which is a lot of people, including me).
You'll still need to add a line to the feed source code.
Browsers really should have embraced XSLT rather that abandoned it. Now we're stuck trying yet again to reinvent solutions already handled by REST [1].
[1] https://tonysull.co/articles/mcp-is-the-wrong-answer/
XSLT is the solution domain specialists and philosophers. Abandoning it is the vote of the market and market interests, the wisdom of crowds at work. This is the era of scale not expertise, enjoy the fruits.
Its more the market makers that made the vote rather than the market itself.
3 replies →
RSS.style is my site. I'm currently testing a JavaScript-based workaround that should look just like the current XSLT version. It will not require the XSLT polyfill (which sort-of works, but seems fragile).
One bonus is that it will be easier to customize for people that know JavaScript but don't know XSLT (which is a lot of people, including me).
You'll still need to add a line to the feed source code.