> You can have natural scrolling, an accurate reader view, a working back button and other highly performant features in a mobile-optimized HTML and CSS standar

> You can have natural scrolling, an accurate reader view, a working back button and other highly performant features in a mobile-optimized HTML and CSS standard like AMP. In fact, you practically have to go out of your way to break these things in the way that AMP does. > Why does AMP have to suck so much? Because it violates every assumption on how browsers should work. I would prefer a slow browser I understand to a fast one I can't control.