> Happy to have a technical discussion, but not sure you are reallty interested.
This is not about technology. And whatever goal the AMP project states it has could have been achieved - and better - in other ways, such as the suggestion elsewhere in this thread to simply penalize page weight. If people wanted a consistent user interface across all websites they would have stuck with Videotext.
> TL;dr AMP is 100% build on web tech.
Yes, so was the search engine that put each result page in an iframe. Only difference was they didn't have a monopoly on search. And it does not make it right.
> Pre-rendering achieves the performance but relies on history.pushState and iframes, which doesn't allow presenting a URL that is not on the same origin as the search page.
Minor technical details, not relevant. If you feel the AMP discussion is going to be swayed by technical bits you're simply out of touch.
> We think that the UX trade off in the URL is OK given the performance benefits.
Who made you the deciders of what the UX of the web should look like? Stick to generating the best search results rather than trying to co-opt the entire web one little bit at the time and leave the UX to the browsers, it would seem you have enough input there already.
> Given that it is a trade off we now have a bunch of projects to mitigate those trade offs.
The only trade-off that will satisfy me is AMP dying off because websites will stop to support it. But as long as Google is strong-arming content providers to use AMP that won't happen. It is no longer fair play as far as Google is concerned. If it ever was.
> My team works directly on WebKit to fix bugs that affects AMP (but also the web as a whole, since AMP is just web tech).
Consider doing something more useful with your talents. For instance, fix the long standing issue with the SERPs that makes it impossible to cut-and-paste URLs pointing to PDFs.