Fight back against Google AMP (2018)

I strongly agree. Web developers and app designers should work to build fast, performant web sites that use bandwidth carefully because that's good for end users. But the entire AMP approach to doing this is questionable, and as we have seen over the years it appears to act more like a way to give Google more undeserved and unnecessary control over what should be an open web. More broadly, I consider this yet another reason to avoid using Google properties…

I don't like AMP at all and fully agree with all the lock-in concerns - but I didn't find this post particularly convincing. This reads in places like a developer or publisher who has grown accustomated to stuffing his pages with gobs and gobs of javascript and questionable UI patterns and is now outraged at the prospect that someone wants to take that privilege away from him. I can't agree with that. Examples: > The underlying message is clear: Google…

An uneducated take from [2018], which you followed up with another poorly written blog post from 2018 (https://news.ycombinator.com/item?id=32617614). This is just low effort karma farming.