Hacker News Reader

Comment by SquareWheel | Hacker News Reader

I'm sorry but if you believe AMP breaks web standards, then you do not understand AMP. It is built entirely from the ground up on web standards.

View on HN

AMP does not work unless you include a Google hosted JS file.

From https://amp.dev/documentation/guides-and-tutorials/learn/spe...:

> AMP HTML documents MUST

> ...

> contain a <script async src="https://cdn.ampproject.org/v0.js"></script> tag inside their head tag.

That is not a web standard.

Wow that is disgusting. Why does it need to include remote code to function? How can they even pretend this is an open standard when it has a backdoor?

It's a subset of HTML, built on WebComponents. The subset is defined by a separate standards board and built on web technologies.

Signed HTTP Exchanges? https://mozilla.github.io/standards-positions/

You're completely exaggerating. Please educate yourself by reading the full conversation leading up to the "harmful" tag before spamming that link again: https://github.com/mozilla/standards-positions/issues/29

The point there is that is it not supported by Mozilla. Google has strong-armed publishers into implementing their websites in a restricted Google format that speeds up websites just for Google Chrome and Google Chromium-based browsers. It's an unethical power grab by Google on multiple levels.

Yes, that's a standard signed by the IETF. It's also an incredibly new feature (supported by AMP starting today).

It's not an actual standard if it's forced on everyone by a single vendor abusing its market dominance.

Reply on news.ycombinator.com