The power to make significant decisions in the AMP Project will move from a single Tech Lead to a Technical Steering Committee (TSC) which includes representatives from companies that have committed resources to building AMP, with the end goal of not having any company sit on more than a third of the seats.
Google is moving the AMP project to a new, more open governance model, which should address some of the valid concerns people have over the project’s Google-centric nature. Google is further exploring creating a separate foundation for AMP, to further solidify the independent nature of AMP. Meanwhile, Microsoft is also adopting AMP by redirecting Bing search results to AMP pages.
Ugh. It’s bad enough that the new Web Components part of normal HTML defines inheritance from an existing element via CustomElementRegistry.define() (a JavaScript call), so it can’t be used in gracefully degrading designs.
I really wish we didn’t need something this NIH just to force web developers to not be so heavy with the crud.
Edited 2018-09-20 23:31 UTC
Maybe we need an AMP rating for web developers – inversely proportional to the percentage performance improvement due to AMP.
If a web developer’s AMP rating is high, they get a pay cut.
The problem is that it’s often not their fault. It’s their bosses demanding that they pile in a ton of ad crud, analytics crud, and other sorts of crud, and to do it by yesterday, regardless of how much “abstractions for the abstractions” garbage they need to meet the deadline.
AMP just gives them a way to tell the higher-ups “It’s out of my hands. Take it up with Google.”
Edited 2018-09-21 05:55 UTC