Hmm, while some of the critic i see here may be valid and justified, i like the enforcing of this strict rule set... i am senior frontend-dev and imho we would

Hmm, while some of the critic i see here may be valid and justified, i like the enforcing of this strict rule set... i am senior frontend-dev and imho we wouldn't need AMP if in 99% of the cases devs, or better their customers would give a damn about doing their job right ( most of the time they just don't know better, because they are just beginners and never learned much about 'advanced' html/css - i haven't seen to much senior devs lowering themself to do html/css work and/or are knowleadgable in this areas ). Most of AMPs advantages regarding FOUC, Jumping-Content and Performance is to enforcing good HTML/CSS practices. Again citing guardian as example... So at least know i have a way to simple enforce a minimum best practice for mobile pages... Whenever i had to sign off a responsive/adaptive mobile page loading 'insane' amounts of unused styles and/or javascript i wanted to hit something with a hammer... I am for giving it some time and see how it develops..