News for hackers. Stuff that matters.
Re:Chrome intends to remove XSLT from the HTML spec by BoiledCabbage on Tuesday August 19, 2025 @12:16PM (#44953260)
So if in reading the two threads correctly essentially Google asked for feedback, essentially all the feedback said "no, please don't". And they said "thanks for the feedback, we're gonna do it any way!"?

The other suggestions ignored seemed to be "if this is about security, then fund the OSS, project. Or swap to a newer safer library, or pull it into the JS sandbox and ensure support is maintained." Which were all mostly ignored.

And "if this is about adoption then listen to the constant community request to update the the newer XSLT 3.0 which has been out for years and world have much higher adoption due to tons of QoL improvements including handling JSON."

And the argument presented, which i don't know (but seems reasonable to me), is that XSLT supports the open web. Google tried to kill it a decade ago, the community pushed back and stopped it. So Google's plan was to refuse to do anything to support it, ignore community requests for simple improvements, try to make it wither then use that as justification for killing it at a later point.

Forcing this through when almost all feedback is against it seems to support that to me. Especially with XSLT suddenly/recebtly gaining a lot of popularity and it seems like they are trying to kill it before they have an open competitor in the web.

https://github.com/whatwg/html/issues/11523

Re:Chrome intends to remove XSLT from the HTML spec by pjmlp on Tuesday August 19, 2025 @12:29PM (#44953383)
Web is for all practical purposes ChromeOS, but then people complain about Apple not playing ball.
Re:Chrome intends to remove XSLT from the HTML spec by nativeit on Tuesday August 19, 2025 @12:37PM (#44953472)
> ChromeOS is for all practical purposes, the web.

Fixed that typo for you.

Re:Chrome intends to remove XSLT from the HTML spec by danans on Tuesday August 19, 2025 @12:50PM (#44953593)
> > ChromeOS is for all practical purposes, the web

I'm very practically using Debian Linux on ChromeOS to develop test and debug enterprise software. I even compile and run some native code. It is very much more than just the web.

Re:Chrome intends to remove XSLT from the HTML spec by pjmlp on Tuesday August 19, 2025 @01:28PM (#44954006)
That is a VM, and actually maybe eventually it will be on top of Webassembly, how things are going.
Re:Chrome intends to remove XSLT from the HTML spec by danans on Tuesday August 19, 2025 @02:09PM (#44954466)
> That is a VM...

So is WSL on Windows. I wouldn't call Windows "just the web".

There's also nothing stopping me from building and running local desktop GUI software on the VM.

In fact, a VM is better in that I can back up and restore the image easily.

Re:Chrome intends to remove XSLT from the HTML spec by pjmlp on Tuesday August 19, 2025 @03:01PM (#44955034)
WSL and other VMs are the Year of Desktop Linux finally coming true, nothing to do with Web.
Re:Chrome intends to remove XSLT from the HTML spec by danans on Tuesday August 19, 2025 @05:10PM (#44956292)
> WSL and other VMs are the Year of Desktop Linux finally coming true, nothing to do with Web.

Just like the Linux VM on ChromeOS.

Re:Chrome intends to remove XSLT from the HTML spec by pjmlp on Wednesday August 20, 2025 @01:09AM (#44958800)
Which eventually will be a VM on top of WebAssembly, given the hype.

https://webvm.io/

Re:Chrome intends to remove XSLT from the HTML spec by danans on Thursday August 21, 2025 @09:31PM (#44980182)
> Which eventually will be a VM on top of WebAssembly,

I'm not sure how that supports the argument that ChromeOS is only "the web". It's running a native VM for Linux today. What would be the advantage of porting it to WebAssembly?

Re:Chrome intends to remove XSLT from the HTML spec by notatoad on Tuesday August 19, 2025 @12:49PM (#44953583)
>essentially all the feedback said "no, please don't". And they said "thanks for the feedback, we're gonna do it any way!"?

this is a perfectly reasonable course of action if the feedback is "please don't" but the people saying "please don't" aren't people who are actually using it or who can explain why it's necessary. it's a request for feedback, not just a poll.

Re:Chrome intends to remove XSLT from the HTML spec by LegionMammal978 on Tuesday August 19, 2025 @01:23PM (#44953956)
> people who are actually using it

I'd presume that most of those people are using it in some capacity, it's just that their numbers are seen as too minor to influence the decision.

> explain why it's necessary

No feature is strictly necessary, so that's a pretty high standard.

Re:Chrome intends to remove XSLT from the HTML spec by kstrauser on Tuesday August 19, 2025 @01:40PM (#44954143)
> I'd presume that most of those people are using it in some capacity, it's just that their numbers are seen as too minor to influence the decision.

I think the idea of that is reasonable. If I used XSLT on my tiny, low-traffic blog, I think it's reasonable for browser devs to tell me to update my code. Even if 100 people like me said the same thing, that's still a vanishingly small portion of the web, a rounding error, protesting it.

I'd expect the protests to be disproportionate in number and loudness because the billion webmasters who couldn't care less aren't weighing in on it.

Now, I'm not saying this with a strong opinion on this specific proposal. It doesn't affect me either way. It's more about the general principle that a loud number of small webmasters opposing the move doesn't mean it's not a good idea. Like, people loudly argued about removing <marquee> back in the day, but that happened to be a great idea.

Re:Chrome intends to remove XSLT from the HTML spec by LegionMammal978 on Tuesday August 19, 2025 @01:49PM (#44954240)
True, a small number of vocal opponents does not automatically make something a bad idea. But in these cases of compatibility, especially with something as big as the Web, the vast majority of those affected who do care will be completely silent. There's no hotline to call up the entire world and tell them to update their code.

(And if you did want to tell the entire world to update their code, and have any chance of them following through with it, you'd better make sure there's an immediate replacement ready. Log4Shell would probably still be a huge issue today if it couldn't be fixed in place by swapping out jar files.)

Re:Chrome intends to remove XSLT from the HTML spec by basscomm on Tuesday August 19, 2025 @02:40PM (#44954806)
> If I used XSLT on my tiny, low-traffic blog, I think it's reasonable for browser devs to tell me to update my code.

I _do_ use XSLT on my tiny, low-traffic blog, and I _don't_ think that it's reasonable for browser devs to tell me to update my code.

Also, it's real easy to manufacture a situation where adoption of a thing is low when the implementation is incomplete and hasn't had significant updates for decades.

Re:Chrome intends to remove XSLT from the HTML spec by tsimionescu on Tuesday August 19, 2025 @04:22PM (#44955903)
The web has grown a thousand fold over those decades, in spite of no support for XSLT. No browser has failed (or gained market traction) by missing support for (or adding more support for) XSLT. It's an irrelevancy, even if you did like it once.

Lots of content was lost when Flash was removed as well - much, much more than the amount of content that will be lost if XSLT is removed. And yet the web continued.

Re:Chrome intends to remove XSLT from the HTML spec by ttepasse on Tuesday August 19, 2025 @06:40PM (#44956912)
... in a diminished state.
Re:Chrome intends to remove XSLT from the HTML spec by chownie on Wednesday August 20, 2025 @08:34AM (#44961333)
The web is straight up a weaker, worse more closed off experience post-flash, so I'm not sure that this engenders the kind of response you had envisioned but now I'm worried about xslt.
Re:Chrome intends to remove XSLT from the HTML spec by zahlman on Tuesday August 19, 2025 @04:05PM (#44955729)
Well, no; the reasonable course of action is to solicit feedback from the right people instead.
Re:Chrome intends to remove XSLT from the HTML spec by notatoad on Tuesday August 19, 2025 @11:15PM (#44958333)
yeah! they should only ask for feedback from people who love XSLT, other people's opinion doesn't matter.
Re:Chrome intends to remove XSLT from the HTML spec by cholantesh on Tuesday August 19, 2025 @01:28PM (#44954013)
You're literally commenting on a thread full of those explanations that were handwaved away.
Re:Chrome intends to remove XSLT from the HTML spec by troupo on Wednesday August 20, 2025 @01:49AM (#44958988)
Google's own document says numbers don't show the full picture: https://news.ycombinator.com/item?id=44956267

They didn't even do the tiniest bit of research, as people in the discussions clearly showed, and there are high impact sites that would be affected by this including Congress and Library of Congress: https://news.ycombinator.com/item?id=44958929

Re:Chrome intends to remove XSLT from the HTML spec by stuaxo on Wednesday August 20, 2025 @06:13AM (#44960501)
Part of the reason I stopped was lack of higher than 1.0 in browsers.

The other reason is that SVG took a very long time to get good, and when it did I wanted to use XSL and SVG together.

Now SVG has got good and they are removing it :(

Re:Chrome intends to remove XSLT from the HTML spec by webstrand on Tuesday August 19, 2025 @12:50PM (#44953588)
It would be incredible if we could pull it into the javascript/wasm sandbox and get xslt 3.0 support. The best of both worlds, at the cost of a performance hit on those pages, but not a terrible cost.
Re:Chrome intends to remove XSLT from the HTML spec by NoGravitas on Tuesday August 19, 2025 @01:16PM (#44953877)
This is clearly the Right Thing. So what do you suppose the chance of it happening is?
Re:Chrome intends to remove XSLT from the HTML spec by bilog on Tuesday August 19, 2025 @05:39PM (#44956510)
There's even a JS implementation of XSLT 3.0 already (SaxonJS).
Re:Chrome intends to remove XSLT from the HTML spec by webstrand on Tuesday August 19, 2025 @05:52PM (#44956610)
That's pretty cool, its too bad the license is a bit confusing about whether bundling with Chrome or Firefox would be permissible under the license.
Re:Chrome intends to remove XSLT from the HTML spec by dev0001 on Wednesday August 20, 2025 @02:06AM (#44959091)
Not really, because that would add a dependency on Javascript whereas, at the moment, XSLT works without Javascript enabled.
Re:Chrome intends to remove XSLT from the HTML spec by dpassens on Wednesday August 20, 2025 @07:00AM (#44960715)
Not necessarily. The idea is that this is browser-internal, so presumably it would still work even if JS from external sources is disabled.
Re:Chrome intends to remove XSLT from the HTML spec by colejohnson66 on Thursday August 21, 2025 @09:36AM (#44972620)
No. The idea is that website authors do the work. The proposal suggests the browsers wholesale remove support and forget about it.

https://github.com/whatwg/html/issues/11523#issuecomment-315...

Re:Chrome intends to remove XSLT from the HTML spec by dpassens on Thursday August 21, 2025 @11:58AM (#44974360)
Oh, I understand that that's the WHATWG proposal. I'm talking about webstrand's idea.
Re:Chrome intends to remove XSLT from the HTML spec by insin on Tuesday August 19, 2025 @12:50PM (#44953600)
Google tells you what they're going to do to the web with a question mark on the end.
Re:Chrome intends to remove XSLT from the HTML spec by cryptonector on Tuesday August 19, 2025 @02:02PM (#44954391)
It's called uptalking.
Re:Chrome intends to remove XSLT from the HTML spec by cess11 on Tuesday August 19, 2025 @12:52PM (#44953613)
It comes with the XML territory that things have versioned schemas and things like namespaces, and can be programmed in XSLT. This typically means that integrations are trivial due to public, reliable contracts.

Unlike your average Angular project. Building on top of minified Typescript is rather unreasonable and integrating with JSON means you have a less than reliable data transfer protocol without schema, so validation is a crude trial and error process.

There's no elegance in raw XML et consortes, but the maturity of this family means there are also very mature tools so in practice you don't have to look at XML or XSD as text, you can just unmarshal it into your programming language of choice (that is, if you choose a suitable one) and look at it as you would some other data structure.

Re:Chrome intends to remove XSLT from the HTML spec by arp242 on Tuesday August 19, 2025 @03:38PM (#44955452)
> all the feedback said "no, please don't"

Thread was already locked due vitriol, insults, and general ranting before I had the chance to comment to say I felt it was a good idea. Also, "this is a good idea" is not really the sort of things people tend to comment, so it will always be biased towards people who disagree. What "all feedback" said on that thread is basically meaningless – it's not a vote.

The fastest way to be dismissed is to be a dick. People were massive dicks so they were dismissed. You all made your bed, so now you have lie in it.

Re:Chrome intends to remove XSLT from the HTML spec by dev0001 on Wednesday August 20, 2025 @02:01AM (#44959065)
The vast majority of feedback on the GitHub issue was respectful — unless you consider opposing the proposal disrespectful.
Re:Chrome intends to remove XSLT from the HTML spec by whimsicalism on Wednesday August 20, 2025 @02:16AM (#44959151)
There’s not nearly enough comments for “vast majority” to be a useful descriptor, and I saw a significant number of uncivil, rude comments.