Hacker News new | ask | show | jobs
by dkiebd 297 days ago
3. It will eventually be removed. Does it matter whether it will take three months or three years? Since I suppose none of the browser vendors will give developers money to change their xslt usage in codebases for something else.

5. Funny that we are talking about "info that leaks to the public" when we are discussing standards that may be important to billions of people, as if keeping things private was reasonable.

6 comments

> Funny that we are talking about "info that leaks to the public"

It's a poor choice of words by the GP. This was a public discussion, what would be private about it?

Rather it "leaked" from people with shared context to people without it. The point of the article is that since the discussion is public, there will be people that come across it without context, so it would be a good idea to include context in these kinds of discussions in the future:

> If a removal discussion is going to be held in public, then it should assume the general public will see it and provide enough context for the general public to understand the actual nature of the discussion.

> Does it matter whether it will take three months or three years?

It does!

I run a small hobby site built with XML and XSLT because I'm not a great programmer, but XSLT is something I can actually wrap my head around and use without too much fuss. If support goes away I need to know how much time I have to rewrite/migrate my site to something else.

I find it bizarre. I think we obviously we want to be able to run pages from 2015 far in the future but certainly for a few more years.

As a browser maker, why would you even put this work in for cordinated processes instead of investing in a way to patch away your native code and do that continuously at a slow pace for every aging feature?

> Since I suppose none of the browser vendors will give developers money to change their xslt usage in codebases for something else.

Let's turn that around: are you willing to pay a browser vendor to keep supporting xslt so you can keep your codebase unchanged?

> Does it matter whether it will take three months or three years?

Do you think it matters to the guy that said he has an entire factory with IoT machinery that uses XSLT?

Should they shut the factory down?

I wish there was a way to fund XSLT feature in browsers. Chrome team should just open up a funding for features page.