Hacker News new | past | comments | ask | show | jobs | submit login

Both of those websites include APIs that were implemented unilaterally by Google, while both Mozilla and Apple rejected them – mostly on privacy and security grounds. They aren’t a part of the web platform and aren’t on any standards track, they are Google APIs.



These APIs are implemented in Chromium, included in a lot of browsers (Chrome, Edge, Opera, Vivaldi, etc.), and used by thousands of web apps.

They are absolutely part of the web platform.


The web platform is not defined as “whatever Google chooses to implement”. It’s a collaborative effort.

All of those browsers use Blink, Google’s rendering engine. It’s one single implementation. Something needs two independent implementations to become a web standard. If you look at the specifications, they will explicitly state that they aren’t standards.

An interoperability project isn’t going to consider working on things that have been explicitly rejected by every implementer but one. That’s not how interoperability happens.

Google need to go back to their specifications and resolve all the security and privacy problems with them so that they can convince at least one other rendering engine to implement them. If they can't do that, there’s no chance they are candidates for interoperability work.




Consider applying for YC's W25 batch! Applications are open till Nov 12.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: