5 ms·
The cause is good, but AMP are overcomplicated. They rely heavily on JS, Web Components, Custom Elements. They need a polyfill for other browsers which don't su
by niutech 11y ago
The cause is good, but AMP are overcomplicated. They rely heavily on JS, Web Components, Custom Elements. They need a polyfill for other browsers which don't support Web Components natively. They add too much bloat to HTML: custom attributes, weird <style>body {opacity: 0}</style><noscript><style>body { opacity: 1}</style></noscript>, etc.
Instead, content providers should stick to plain old HTML with a small CSS script and no JS, just like RSS feeds. That would be blazing fast and backwards compatible.
- bduerst 11y agoDoesn't the lack of js make it impossible for content creators to provide ad-subsidized content?
- niutech 11y agoNo, the ads could perfectly be like: <a href="..."><img src="..." alt=".."></a> with src generated server-side.
- bduerst 11y ago>perfectly That would kill any targeting, thus destroying conversion rates on cpc ads and diminishing the value of display ads. This perfect system would lead to more spammy ads, not less. Content creators aren't going to jump on that. And do exchanges actually let publishers dynamically serve ad content from server-side? Wouldn't they be able to fake impressions?
- zukee 11y agoNo, there is built in support for ads in the AMPHTML framework, see: https://github.com/ampproject/amphtml/blob/master/builtins/amp-ad.md https://github.com/ampproject/amphtml/blob/master/builtins/a...