> Maciej Cegłowski already recreated the Google AMP demo page
He solved a different problem.
I don't think anybody at AMP claims that fast pages aren't possible. Their claim is that there's a need to enforce certain rules to achieve a certain quality of service.
> teach people how to make their sites faster
In a way, that's what AMP is doing. It picks a subset of HTML5 that can be rendered efficiently, and - for now - uses javascript to fill in the blanks (eg. where desired capabilities are forbidden due to how they're commonly implemented: provide build a polyfill that's better suited) and for enforcement of these rules.
As linked in my parent post, there are already efforts to offload some of these constraints into standards to be enforced by browsers - I fully expect the AAMP scaffolding to let go of that soon after (or revert to shims)
He solved a different problem.
I don't think anybody at AMP claims that fast pages aren't possible. Their claim is that there's a need to enforce certain rules to achieve a certain quality of service.
> teach people how to make their sites faster
In a way, that's what AMP is doing. It picks a subset of HTML5 that can be rendered efficiently, and - for now - uses javascript to fill in the blanks (eg. where desired capabilities are forbidden due to how they're commonly implemented: provide build a polyfill that's better suited) and for enforcement of these rules.
As linked in my parent post, there are already efforts to offload some of these constraints into standards to be enforced by browsers - I fully expect the AAMP scaffolding to let go of that soon after (or revert to shims)