3 ms·

I mentioned this before, but the only problem I have with AMP is that one can't self-host - you have to link to amp js files on the official servers (you'd thin

I mentioned this before, but the only problem I have with AMP is that one can't self-host - you have to link to amp js files on the official servers (you'd think a starting point for fast hosting of webpages would be hosting everything on the same server, but it seems no...). I haven't seen anyone try to justify this; for whatever reason it's not on anyone else's radar that I've seen. For me it's a total deal-breaker. If you want a standard you can specify a standard, if you want a framework you can specify a framework. But requiring it to give you client-side permission to run scripts is something that requires more justification that I've seen anyone give. (I haven't checked the official amp website in a year or so, maybe things have changed since then).

BrianOnHN 6y ago
Self-hosting is a thing, at least as far as the amp-geo component is concerned: > Publishers and caches that re-host AMP JavaScript files... https://amp.dev/documentation/components/amp-geo/#self-hosting https://amp.dev/documentation/components/amp-geo/#self-hosti...
- jan_Inkepa 6y ago
  Huh. Interesting! https://github.com/ampproject/amphtml/blob/master/spec/amp-framework-hosting.md https://github.com/ampproject/amphtml/blob/master/spec/amp-f... says that as of April 2020 self-hosted pages don't pass validation: >The AMP Project is looking into options for validation of AMP pages that use an AMP framework hosted outside of cdn.ampproject.org (#27546). As of April 2020, these AMP pages do not pass validation. The linked issue is still open: https://github.com/ampproject/amphtml/issues/27546 https://github.com/ampproject/amphtml/issues/27546 And if I look at the official Specs page ( https://amp.dev/documentation/guides-and-tutorials/learn/spec/amphtml/ https://amp.dev/documentation/guides-and-tutorials/learn/spe... ) it says this: > Any AMP document MUST [...] contain a <script async src="https://cdn.ampproject.org/v0.js"></script> https://cdn.ampproject.org/v0.js"></script> tag inside their head tag. So it seems they're planning on supporting self-hosting, but it's not there yet (and it might be complex to get working).
maxfurman 6y ago
I think the justification is something along the lines of "Google's cache is faster than yours" - but I also agree that it's a bridge too far. I should be able to add a <meta> tag in my header that says "this is an AMP page" and assuming I've implemented AMP correctly that should be enough.
Chris2048 6y ago
surely if you have a js asset on one, official server, then it will just be cached once and you'll never have to serve it at all after that, and as such serving it "fast" isn't the issue?

BrianOnHN 6y ago

Self-hosting is a thing, at least as far as the amp-geo component is concerned: > Publishers and caches that re-host AMP JavaScript files... https://amp.dev/documentation/components/amp-geo/#self-hosting https://amp.dev/documentation/components/amp-geo/#self-hosti...

jan_Inkepa 6y ago
Huh. Interesting! https://github.com/ampproject/amphtml/blob/master/spec/amp-framework-hosting.md https://github.com/ampproject/amphtml/blob/master/spec/amp-f... says that as of April 2020 self-hosted pages don't pass validation: >The AMP Project is looking into options for validation of AMP pages that use an AMP framework hosted outside of cdn.ampproject.org (#27546). As of April 2020, these AMP pages do not pass validation. The linked issue is still open: https://github.com/ampproject/amphtml/issues/27546 https://github.com/ampproject/amphtml/issues/27546 And if I look at the official Specs page ( https://amp.dev/documentation/guides-and-tutorials/learn/spec/amphtml/ https://amp.dev/documentation/guides-and-tutorials/learn/spe... ) it says this: > Any AMP document MUST [...] contain a <script async src="https://cdn.ampproject.org/v0.js"></script> https://cdn.ampproject.org/v0.js"></script> tag inside their head tag. So it seems they're planning on supporting self-hosting, but it's not there yet (and it might be complex to get working).

maxfurman 6y ago

I think the justification is something along the lines of "Google's cache is faster than yours" - but I also agree that it's a bridge too far. I should be able to add a <meta> tag in my header that says "this is an AMP page" and assuming I've implemented AMP correctly that should be enough.

Chris2048 6y ago

surely if you have a js asset on one, official server, then it will just be cached once and you'll never have to serve it at all after that, and as such serving it "fast" isn't the issue?