- standards they write themselves that everyone ignores - standards they copy from the WHATWG
[0]https://en.wikipedia.org/wiki/Verifiable_credentials [1]https://en.wikipedia.org/wiki/Decentralized_identifier [2]https://en.wikipedia.org/wiki/JSON-LD
The XML and related specs are implemented by various applications and libraries even if web browsers dislike these specs. -- They are used a lot in document publishing workflows that use formats like JATS, and are supported by various tools and libraries.
SVG is widely supported in vector graphics applications and rendering tools.
And WHATWG hasn't just co-opted W3C specs -- it's also co-opted encoding, URIs and others from places like the RFCs.
CSS, WAI-ARIA, SVG, WebGPU, WebAuthn...and a large number of APIs that are referenced as part of the HTML spec but developed and standardized by different W3C groups.
> standards they copy from the WHATWG
Not for six years now: https://www.w3.org/blog/2019/w3c-and-whatwg-to-work-together...
Lots of hn people need to update their priors about modern web standardization work.
zb3•9mo ago
Y-bar•9mo ago
Etheryte•9mo ago
fuzzzerd•9mo ago
zcw100•9mo ago
zelon88•9mo ago
vntok•9mo ago
That page is probably among the top 3 most analyzed, optimized and A/B tested webpages in the world.
zelon88•9mo ago
Google controls the browser, the page, the CDN, AND to a large extent the very standards that the browser has to comply with.
If what you claim is true, with all of this authority, why can't they write a compliant web page?
fouc•9mo ago
It could be a way to keep some kind of competitive edge or some kind of fingerprinting strategy or for some other reason altogether.
vntok•9mo ago
I'm not sure why you'd think that they "can't" write a compliant web page. It's obvious they can, just like it's obvious they've been paying a bunch of experts top dollars for multiple decades to think about and test what exactly to write in this page's code. It's also obvious they've taken into account the basic fact that every character* they add costs them a measurable amount of money to serve given their scale.
It's therefore pretty obvious that they're deliberately choosing to write a non-compliant web page. Presumably because among the multiple billions of users they serve this page to, a high-enough-to-matter portion is still using old and/or non compliant web browsers and they don't want to cut them out.
* past certain packet length cutoffs
pjmlp•9mo ago
They even ship Chrome with their applications, because people can't be bothered to learn neither native UI frameworks, nor portable Web standards.