AMP: the missing controversy
We were discussing with the AMP project tech lead over on GitHub trying to suss out details about governance and the like, and it&#x27;s even scarier than we thought when it came to AMP4Email: Gmail is implementing AMP in email &quot;the way they want to&quot;, and AMP Project is just deciding whether or not they want to support it&#x2F;publish a &#x27;standard&#x27;.<p>I strongly recommend this for reading: <a href="https:&#x2F;&#x2F;github.com&#x2F;ampproject&#x2F;amphtml&#x2F;issues&#x2F;13597" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;ampproject&#x2F;amphtml&#x2F;issues&#x2F;13597</a> (locked, sadly) and the original AMP4Email issue has a fair bit as well: <a href="https:&#x2F;&#x2F;github.com&#x2F;ampproject&#x2F;amphtml&#x2F;issues&#x2F;13457" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;ampproject&#x2F;amphtml&#x2F;issues&#x2F;13457</a> (only for discussion of email).<p>Unfortunately, there are lots of people talking about how bad AMP is, and why, but nobody yet has suggested how we do anything to stop it.