4 ms·
> I don't think this is hostile to developers at all, unless AMP is already hostile. I think the prevailing opinion on Hacker News is exactly that.
by reificator 9y ago
> I don't think this is hostile to developers at all, unless AMP is already hostile.
I think the prevailing opinion on Hacker News is exactly that.
- tree_of_item 9y agoI don't see how a subset of HTML could be hostile. AMP is not Google Search.
- krapp 9y agoA subset of HTML isn't hostile. A browser that defaults to only rendering that subset is hostile, because it relegates any content which doesn't conform to that proprietary spec to second-class status.
- baddox 9y agoMy impression is that HN’s hostility toward AMP is caused less by the spec itself and more by Google’s leverage of its market power in search to incentivize AMP adoption, as well as its “web-breaking” behavior (like sending you to ugly and self-serving google.com/amp/whatever URLs).