4 ms·
> #2: “AMP is a Google project” This is not a misconception. Literally every AMP "Core Committer" is a Google employee, all contributions are subject to a Goog
by callahad 10y ago
> #2: “AMP is a Google project”
This is not a misconception. Literally every AMP "Core Committer" is a Google employee, all contributions are subject to a Google CLA which includes a patent grant, every AMP page must include a third party script hosted by Google, and it's impossible to opt-out of Google's AMP Cache, which preferentially links to and re-hosts your content on Google's servers instead of allowing you to receive and analyze your own traffic.
AMP allows outside contribution, but it is absolutely a Google project.
Edit: This point seems especially disingenuous since the author is a Google employee in Developer Relations: https://paulbakaus.com/about/ https://paulbakaus.com/about/. His job role is literally "Web Advocacy lead for AMP" https://www.linkedin.com/in/paulbakaus https://www.linkedin.com/in/paulbakaus.
- Semiapies 10y agoYeah, that went over the line of honest advocacy for me, too.
- hood_syntax 10y ago> the author is a Google employee in Developer Relations Haha, wow. And I didn't even know about the caching behavior, that's ridiculous.
- blowski 10y agoGood catch. I started out by thinking you were being pedantic, but I can see that you're right. The author needs to be more transparent, and I didn't realise how much of a Google project it is. I had thought it was like Angular and Go.
- niftich 10y agoA good way to test the theory whether AMP is a Google Project is to submit a pull request to allow the import location of the AMP runtime to be configured.