Second is the article which led me to Lighthouse in the first place: AMPersand, by Ethan Marcotte. Not much to add to this one, just another voice adding weight to my uneasiness with the idea of AMP and similar projects. Well worth a read if you're interested in the open web.
Few corporations have done as much as Google to elevate the importance of page speed as a design issue, and the work done by the AMP team is no exception. But in my experience, the only voices promoting AMP’s performance benefits are coming from inside Google.
Note: this was originally part of a full article titled "Stickers, Eclipses and Lighthouses" and the 36th post in my New 52 challenge. That article also linked to a (then) new tool called Google Lighthouse, a design collection of achievement stickers for developers, a look at time management, and a critique of data visualisation of future solar eclipses.
