So, instead of a giant corporation with all the resources in the world stepping in and maintaining a core web library, they're deciding to remove a feature because the lone maintainer who has been doing a thankless job for years has decided to unsurprisingly step down from this role.
I suppose we can expect support for XML to be dropped soon as well, since libxml2 maintenance is ending this year.
I don't buy the excuse of low number of users. Google's AMP has abysmal usage numbers, yet they're still maintaining that garbage.
Google has been a net negative for the web, and is directly responsible for the shit show it is today. An entirely expected outcome considering it is steered by corporate interests.
Probably more due to the fact that browsers only support the 1999 XSLT 1.0, and no one has shown any interest in implementing XSLT 2.0 from 2001, or XSLT 3.0 from 2017. So there has been a sign of lack of desire since 2001 at minimum, likewise there is seemingly no attempt by anyone to document incompatibilities and push browsers to unify their incompatibilities like HTML, JS, and CSS.
The writing has been on the wall for a long while. Mozilla hasn't stepped up, Google hasn't stepped up, GNOME hasn't stepped up, Oracle hasn't stepped up, etc. Maybe its just a format that once anyone gets involved with, they no longer want to be involved with it any further.
I would expect governments finally taking over.
I believe they didn’t just because most of politicians don’t know anything about software.
Being aware of the problems that “governmatization” of open source can bring it still is something I expect to be picked up by countries.
People are free to make their own browser if they want.
Part of the reason google chrome won the browser wars is because they are willing to make decisions like this. Kitchen sink software is bad software.
The whole point of browser standards is to avoid every browser picking and choosing features their own features, its a terrible end user experience.
No one should fork chrome and maintain it with XSLT still baked in. Not only would it go unused, it doesn't help anyone wanting to ship XSLT on a site because users would literally have to install a different browser just to see that page.
A kitchen sink software implies an image of a kitchen sink filled with dirty dishes. But the solution is not to throw them all away and leave a single dish, still dirty, but at least looking manageable. The solution is to wash all dishes and put them neatly on the rack.
The idiom "everything but the kitchen sink" (and variant "everything including the kitchen sink") doesn't refer to a sink filled with dirty dishes. Rather, the kitchen sink (originally the kitchen stove) is being used as an example of a particularly bulky item. "Everything but the kitchen sink" means, roughly, everything except for what would be too large and/or absurd to include.
https://english.stackexchange.com/questions/96582/what-is-th...
Really, because mozilla seamonkey tried that. How do you think that went for them?
> People are free to make their own browser if they want.
Some peple are doing that[1]. It's not a matter of desire, but of the amount of effort and resources required to build and maintain the insanity of the modern web stack.
> Part of the reason google chrome won the browser wars is because they are willing to make decisions like this.
Eh, no. Google Chrome won because it is backed by one of the largest adtech corporations with enough resources and influence to make it happen. They're better at this than Microsoft was with IE, but that's not saying much. When it launched it introduced some interesting and novel features, but it's now nothing but a marketing funnel for Google's services.
[1]: https://ladybird.org/
> Some peple are doing that[1]. It's not a matter of desire, but of the amount of effort and resources required to build and maintain the insanity of the modern web stack.
People say that, but i don't think that's true. The web stack was always insane, the only difference is its documented now. I think now is a much easier time to build a web browser than the past was.
Not to mention the irony of complaining the web stack is insane while insisting a really difficult to support feature that never saw much use should be kept forever because reasons.
> Eh, no. Google Chrome won because it is backed by one of the largest adtech corporations with enough resources and influence to make it happen
Google won because nobody else really tried.
Firefox has been a dumpster fire of bad management decisions and has reduced itself to basically just copying google's every decision sacraficing any unique identity of its own.
Safari is never going win when it is mac only and apple doesnt seem to fund it very hard.
Most of the rest are just chrome reskins that dont deserve to be called a separate browser.
Maybe something interesting might come out of ladybird. Its still quite early to tell.
> Google won because nobody else really tried.
Google won because it:
- built on a very solid foundation from the start (it started out as a webkit fork), and was generally a good fast browser. This is the very minor part
- Sabotaged Firefox: https://archive.is/tgIH9
- Heavily promoted and advertised Chrome across all of its properties which included such insignificantly small sites like Google Search and Youtube.
> - Sabotaged Firefox: https://archive.is/tgIH9
Running an advertising campaign is hardly sabotage
You didn't read the link and assumed that my last bullet point refers to sabotage.
Also, you somehow think that running an exclusive directed ad campaign for Chrome on two most popular sites on the internet is nothing to worry about.
Will Ladybird support web standards or just take lead from Google though. Will Ladybird support XSLT?
> Kitchen sink software is bad software.
Ah yes. That's why Chrome bravely refuses to be a kitchen sink. It only has a small set of available APIs like USB, MIDI, Serial, Sensors (Ambient Light, Gyroscopes etc.), HID, Bluetooth, Barcode detection, Battery Status, Device Memory, Credential Management, three different file APIs, Gamepads, three different background sync APIs, NFC...
And it still doesn't support alternate stylesheets, maybe due to NIH syndrome.
Firefox killed the alternate stylesheet UI in like version 1. Nobody really supports alternate stylesheets.
Can you explain what you mean? My Firefox version supports setting alternate stylesheets just fine. It doesn't persist across page reloads, which is annoying though.