2 ms·

> I've never understood the use of AMP, just build your normal site properly in the first place and then you won't need it. It's almost like training-wheels for

> I've never understood the use of AMP, just build your normal site properly in the first place and then you won't need it. It's almost like training-wheels for learning efficiency/optimization. I've never understood why toddlers need training wheels on their bikes? Why don't they just bike properly in the first place?

kup0 11y ago
If your view is that web developers working for publishers are "toddlers" in their industry, then I suppose this comparison is apt. I guess the only oversight I see in my original post is that most of the time, the webdevs aren't the ones with the final say anyway and maybe branding the restrictions will make it more palatable to publishers. It's just sad that we're at the point where it has to be done this way. But it is telling that publishers are fine with being restricted by AMP, when they could have implemented those restrictions extremely easily on their own instead of having to be hand-held through the whole thing. The other issue I have is that it's generally intended for mobile only. If the site was built for speed and efficiency from the ground up, it would be a fast experience everywhere