3 ms·

I'm not convinced of AMP. I've written before on HN about my own webpage[0] were the average page weighs in at around ~10kb. At one point I was working on integ

by K0nserv 10y ago

I'm not convinced of AMP. I've written before on HN about my own webpage[0] were the average page weighs in at around ~10kb. At one point I was working on integrating AMP and some of the constraints from AMP has made it into the site. Ultimately though the 170kb weight of AMP(17x my average page) is a no go. I think imposing the same constraint AMP imposes on you without actually using their JS is a good idea if you aren't after the special treatment from google. Another downside of AMP is that it just display a completely blank page if the user doesn't have JS enable or blocks 3rd-party JS. 0: https://hugotunius.se https://hugotunius.se

esrauch 10y ago
If your pages are 10kb then I think you aren't the target audience for amp. They say themselves that amp pages will never be the most light weight of all pages and never faster then perfectly hand tuned pages, just way way better than the current median website that loads MBs from 75 domains and relayouts 50 times before it's done loading.
- K0nserv 10y ago
  You have a good point all though I'd like to put forth the argument that many websites could just as well focus on reducing their page sizes and external resources instead of/before adopting AMP.
  - esrauch 10y ago
    As an outsider (not remotely in any position to use amp or not) it looks like one of the positive aspects of amp is a utility with some associated carrot and stick to just get publishers to realize those things really are bad and need to be taken seriously.
- kuschku 10y ago
  Well, then Google should also include the search rating bonus and the "fast page" lightning logo for all pages smaller than 170kb directly.
laurent123456 10y ago
The AMP GitHub page claims that "AMP HTML is a way to build web pages for static content". It's ironic that we now need a 170kb Javascript file in order to generate static HTML web pages.
- rakoo 10y ago
  When Sourcegraph's Checkup (https://news.ycombinator.com/item?id=12240380 https://news.ycombinator.com/item?id=12240380) hit HN, I've discovered that the meaning of "static content" changed from "raw HTML with no backend and no frontend rendering" to "HTML + Javascript with no backend but possibly some frontend rendering"
  - networker 10y ago
    It can be even looser than that, it can even just mean any server-side call that is inherently cache-able, meaning the same request will return the same data. "Static" meaning "Not changing over time" rather than "Dynamic" meaning "changing over time". That usage is not common outside of math, but I have on occasion seen it used this way when discussing web programming.

by K0nserv 10y ago

esrauch 10y ago

If your pages are 10kb then I think you aren't the target audience for amp. They say themselves that amp pages will never be the most light weight of all pages and never faster then perfectly hand tuned pages, just way way better than the current median website that loads MBs from 75 domains and relayouts 50 times before it's done loading.

K0nserv 10y ago
You have a good point all though I'd like to put forth the argument that many websites could just as well focus on reducing their page sizes and external resources instead of/before adopting AMP.
- esrauch 10y ago
  As an outsider (not remotely in any position to use amp or not) it looks like one of the positive aspects of amp is a utility with some associated carrot and stick to just get publishers to realize those things really are bad and need to be taken seriously.
kuschku 10y ago
Well, then Google should also include the search rating bonus and the "fast page" lightning logo for all pages smaller than 170kb directly.

laurent123456 10y ago

The AMP GitHub page claims that "AMP HTML is a way to build web pages for static content". It's ironic that we now need a 170kb Javascript file in order to generate static HTML web pages.

rakoo 10y ago
When Sourcegraph's Checkup (https://news.ycombinator.com/item?id=12240380 https://news.ycombinator.com/item?id=12240380) hit HN, I've discovered that the meaning of "static content" changed from "raw HTML with no backend and no frontend rendering" to "HTML + Javascript with no backend but possibly some frontend rendering"
- networker 10y ago
  It can be even looser than that, it can even just mean any server-side call that is inherently cache-able, meaning the same request will return the same data. "Static" meaning "Not changing over time" rather than "Dynamic" meaning "changing over time". That usage is not common outside of math, but I have on occasion seen it used this way when discussing web programming.