3 ms·

FWIW, only the second bullet point applies here > both are a free product that locks users into the company's revenue stream (ads in AMP for Google, Windows fo

FWIW, only the second bullet point applies here > both are a free product that locks users into the company's revenue stream (ads in AMP for Google, Windows for MS) Ads on AMP sites don't have to be from google > both onboarded developers with promises to better user experience while locking them into a non-standard platform. AMP, while a particular subset of HTML/JS, is still just a subset, aka part of the standard platform and can run in any browser. Calling it non-standard would be like calling it non-standard to use React. It's just a library/framework.

laumars 9y ago
> Ads on AMP sites don't have to be from google AFAIK they do if you want to be on the carousel above the search results on Google Search. It's part and parcel of using the Google AMP CDN. Sure you can use other CDNs (even roll your own) but then you do not appear on the AMP carousel above Google search results (which is highly valuable real estate). > AMP, while a particular subset of HTML/JS, is still just a subset, aka part of the standard platform and can run in any browser. Calling it non-standard would be like calling it non-standard to use React. It's just a library/framework. The fact it's a subset makes it non-standard because you cannot then write standard HTML / JS. To flip the argument, this debate started because Chrome was accused of not following standards because it ignores some HTML properties (eg autocomplete). You could argue the same as you were for AMP that Chrome is following a subset. Personally I find it a stretch to argue that x being a subset of the standard means x is a standard.