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

AMP is not open web though. It's Google's own walled garden under the guise of an open web.



As a javascript library it is pretty much as open as React or any other javascript platform.

It is the caching where the discussion lies - effectively Google is providing a CDN for AMP pages and I agree this needs some improvements. But these should in the realm of technical discussions rather than looking for conspiracies.


AMP is designed by Google, and implemented almost exclusively by Google. It is also used in the most popular search engine in a way that makes AMP feel like it's fast.

Meanwhile:

- it's not fast without Google's overpowered cache/CDN (that no one has a chance to replicate)

- it's not even valid HTML

- it's entire design and development is governed exclusively by Google, with no external input, and all external input is discarded and discouraged. See top comment: https://news.ycombinator.com/item?id=16455593

The fact that it lives on GitHub doesn't make it open.


>it's not fast without Google's overpowered cache/CDN (that no one has a chance to replicate)

https://amp.cloudflare.com/

https://blogs.bing.com/search/September-2016/bing-app-joins-...

>it's not even valid HTML

Custom elements are in the WebComponents spec, which is "valid HTML".

https://www.webcomponents.org/introduction#custom-elements


> Links to other implementations

1. Google dominates search. So other caches are basically irrelevant

2. To create a competing cache you need to make sure Google's search uses that cache and that your cache is big, fast, and powerful enough to pre-render AMP pages on Google scale

Which comes back to the original problem: AMP is not fast until someone caches and pre-renders it.

> Custom elements are in the WebComponents spec, which is "valid HTML".

Will all of you "opponents" please read the article you comment on?

Since you can't, here is the six paragraph:

> AMP makes up its own standards that break with what is considered valid HTML. Case in point, have a look at how the AMP project’s homepage, which itself is an AMP page, produces over a 100 validation errors

You can check it yourself.


>Google dominates search. So other caches are basically irrelevant

Then why did you ask to see other caches? You're moving the goalposts.

>produces over a 100 validation errors

By a validator that doesn't understand HTML5. Try your browser - it's a far more advanced version of the validator. You'll find it understands amp pages just fine.


> Then why did you ask to see other caches? You're moving the goalposts.

No goalposts have been moved.

Once again. Slowly:

---- quote -----

AMP is designed by Google, and implemented almost exclusively by Google. It is also used in the most popular search engine in a way that makes AMP feel like it's fast.

Meanwhile: - it's not fast without Google's overpowered cache/CDN (that no one has a chance to replicate)

- it's not even valid HTML

---- end quote ----

You cannot replicate Google's cache for the following reasons:

- Google's search is dominant.

- Google's search uses and will use Google's own AMP cache.

- Google's own AMP cache relies on Google's infrastructure.

Even if you create an AMP-compliant cache:

- Google will not use it.

- It's highly unlikely that you will be able to match its power and speed.

How is AMP open and fast again?

> By a validator that doesn't understand HTML5. Try your browser

Nope. The browser is able to render AMP pages just because the browsers have historically tried to make the best out of shitty HTML.

Let's start from the top.

Do you know that this is invalid HTML 5?

    <html :lightning emoji:>
HTML5 living standard sections 4.1.1 and 3.2.6.

Do you know that this is invalid HTML 5?

    <script async custom-element="amp-carousel" src="">
HTML5 living standard sections 4.12.1 and 3.2.6.

Do you know that this is invalid HTML5?

    <head>
       <style amp-boilerplate></style>
    </head>
HTML5 living standard sections 4.2.6 and 3.2.6.

Shall I continue?

You see, in order to know that it's enough to just stop drinking in Google's propaganda and actually look at what the web has to offer, and how all of this stuff works.




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

Search: