> Do you really like the idea that when you go to some search result it effectively is opening an iframe to the website you're trying to go?
As an end-user or web developer?
As an end-user, I do not care. In fact, it seems that the AMP solution (which isn't an iframe so much as just serving the data from Google's cache at a Google URL) is faster.
> Or as a web developer you need to make sure to adopt to their stupid standards like renaming your img to amp-img and making sure it works in amp and non-amp so you'd be doing both?
As a developer, if I care enough about my user's experience to be bothering with AMP in the first place, I should be using a toolchain that makes it pretty straightforward to go from my meta-representation of my content to the render target (HTML / css, etc.). Because that toolchain should already be doing things like precompiling my CSS, condensing my image data, etc.
As an end-user or web developer?
As an end-user, I do not care. In fact, it seems that the AMP solution (which isn't an iframe so much as just serving the data from Google's cache at a Google URL) is faster.
> Or as a web developer you need to make sure to adopt to their stupid standards like renaming your img to amp-img and making sure it works in amp and non-amp so you'd be doing both?
As a developer, if I care enough about my user's experience to be bothering with AMP in the first place, I should be using a toolchain that makes it pretty straightforward to go from my meta-representation of my content to the render target (HTML / css, etc.). Because that toolchain should already be doing things like precompiling my CSS, condensing my image data, etc.