5 ms·
The fast, non-blocking content loading is the main feature. I took a radical path when developing my site and made it AMP-first. Instead of having an AMP versio
by claudiulodro 9y ago
The fast, non-blocking content loading is the main feature. I took a radical path when developing my site and made it AMP-first. Instead of having an AMP version of each page, every page is its own AMP version because it's an AMP page.
Even served from my cheapo shared web host and not Google's AMP cache, I have pretty-much instant loading of all pages: http://multithreaded.link/2017/08/lyft-customer-acquisition-costs-decrease-uber-stumbles/ http://multithreaded.link/2017/08/lyft-customer-acquisition-...
It's a good framework for building super fast pages. I will admit it's a little riskier to build a site on top of technology a large company owns, but this is a risk that you also have when you use React or other frameworks.
- smt88 9y ago> this is a risk that you also have when you use React or other frameworks React isn't a good analogy. When you use React, you can get 100% of the value of the library, even if Facebook disappears overnight. By contrast, much of the benefit of AMP is the caching aspect, which relies on Google.
- an27 9y agoNice, on FF I get a white page because Google domains lurk in my hosts file. I suppose I'm not your target audience.
- deleted 9y ago[deleted]
- stephenr 9y ago> The fast, non-blocking content loading is the main feature. You don't need requires-js-to-render markup or a cache operated by a privacy whoring ad company to make a page load quickly. Edit: also, comparing to react or whatever js framework is like saying "look at my new cast iron shoes, they're so much lighter than those old lead ones".
- kmoe 9y agoYour "About", "Contact", and "Privacy Policy" footer links don't work (they go to "#").
- claudiulodro 9y agoYeah sorry about that! I just launched it recently so I'm still getting everything going. :)