3 ms·
> It's a documentation site. You want it to pretend the API doesn't exist, or what? MDN is a documentation site for web technologies. In order for something t
by JimDabell 2y ago
> It's a documentation site. You want it to pretend the API doesn't exist, or what?
MDN is a documentation site for web technologies.
In order for something to become a web standard, it needs two independent implementations. If Google can’t build consensus or convince anybody outside of Google to implement it, it’s not a web technology, it’s just some Google API that Google built for Google’s needs.
This is out of scope for a site dedicated to web technologies. This is like expecting them to document Android APIs.
- bastawhiz 2y agoIt's a proposal for a web technology. Every web technology starts as a proposal, even if nobody but a single vendor implements it. MDN includes documentation for serious proposals at all stages, regardless of the standardization process. In fact, MDN includes non-standardized APIs as well. Browser-specific interfaces are included, because it turns out that if you only document the APIs that went through the standardization process and not the ones that actually exist, it makes for a bad documentation site.
- JimDabell 2y agoIt’s a proposal that was rejected by everybody who isn’t Google. It isn’t going to be part of the web platform. It has exited the standardisation process. It’s at stage “never”. It belongs on MDN about as much as JSSS does.
- Dylan16807 2y agoJSSS is long dead. I'd say a better comparison is JSX, and searching for that I do see pages on MDN about it.
- bastawhiz 2y agoThat doesn't change anything. Whether or not it ever ships doesn't mean it shouldn't be documented. There's zero cost to documenting it. Just because you don't like it and it didn't make it past the proposal stage doesn't mean it shouldn't be on MDN. That's not how MDN works.