2 ms·
"Public" web standards my ass. That are only implemented by Chrome, and are at best documenting what Chrome does after the fact. Coming from a self-serving, sel
by tannhaeuser 5y ago
"Public" web standards my ass. That are only implemented by Chrome, and are at best documenting what Chrome does after the fact. Coming from a self-serving, self-acclaimed "standardization" body (WHATWG) consisting of a bunch of Chrome devs, and having never delivered a single finalized spec. Which is now approaching tens of thousands of pages, with thousands of APIs only ever implemented by Chrome that are never going to be implemented by FF and Safari due to privacy (fingerprinting and other) concerns. And are you seriously calling on W3C to spec out even more absurd CSS complexity split out in tens of fragmented specs piled on top of each other, and superseding one another without explicit reference and lacking any formal semantics? Coming from a pay-as-you-go org? That is responsible for the stagnation of the web when they were busy with redefining the "web stack" in the 2000s (in good faith, but still) and consequently lost to Ian Hickson's WHATWG?
If the EU and/or others are interested in standardization and sustainability, they should begin to demand and stick to standards in public services/tenders, and turn to standardization bodies with proper statue to clean up the mess.