Yeah, that's my point. Pale Moon's developers forked a complex project and are now asking people to not use things that the mainline project now supports just fine.

Checks written, can't cash, etcetera.

Fair enough, should have sensed the sarcasm.

There are too many APIs released at neck-breaking speed, often poorly designed and rushed.

See Google's own Web Api tracking page [1] Chrome adds almost 1000 new APIs per year Only last year they added over 500 APIs that are not present in other browsers, and pretend they are standard and will not remove them even if other browsers are not going to implement them due to multiple explicitly voiced concerns.

So yeah, no. Your news at eleven is misleading at best.

[1] https://web-confluence.appspot.com/#!/confluence

> Definition: API: For the purposes of these metrics, an “API” is an interface name + attribute or operation pair.

So there aren’t 1000 new Web Component specs coming out each year, no. And fewer make it into W3C/WHATWG specs.

No. But there are 1000 new web APIs that you have to implement yearly just to keep up. And Web Component specs are a part of that.

And then despite all the objections from all the other browser vendors Google releases an API in production and will not mark it as experimental. Yes, a Web Components-related API (Adopted Stylesheets).