Death comes for XSLT
0 comments · browsers, web
- Comments91
0 comments · browsers, web
Story details from Lobsters ↗ · linked article on dbushell.com.
Death comes for XSLT was first seen on Lobsters · Hottest on Nov 3, 2026. Since then it has appeared in 93 checks on 3 different days. Its best position was #1 of 25, reached on Nov 3, 17:21 UTC. It dropped off the list after Nov 5, 13:21 UTC. The same link also trended on Hacker News, which raises its cross-platform score.
Position on Lobsters · Hottest at every check (lower is better).
Best rank per day (UTC).
Platform metric as reported by Lobsters.
| List | Best | Days | Checks | Last seen |
|---|---|---|---|---|
| Lobsters · Hottest | #1 | 3 | 93 | |
| YHacker News · Front page Death Comes for XSLT | same link | |||
A few top-level comments from Lobsters, shortened. Read the full thread on Lobsters.
> That was not a unilateral decision mind you, Google said “jump” and other browser vendors said “how high?” I’m baffled by this portrayal. As linked, it genuinely *isn’t* just Google: Mozilla and Apple are well-documented as having wanted to kill XSLT for some years, they just lacked the enthusiasm to push it. The…
it kinda is, because it injects unintended code into what was supposed to be delivered from website author to the end-user.
I have mixed feelings because I *really* like the XML document model. It's a tree of nodes where each node has key-value pairs as attributes and zero or more children. Each child is another node or character data. This is a *really* nice generic structure that a huge number of things map to. But the text…
Archived daily, weekly and monthly lists that include this entry.
Not at the moment. It was last on the list on Nov 5, 13:21 UTC, after 3 days of trending.
#1 on Lobsters · Hottest, on Nov 3, 17:21 UTC. Trendoday checks this list every 30 minutes.
It was first seen on Nov 3, 2026 and has been on the list on 3 days (93 checks) since.