News for hackers. Stuff that matters.

A comment on Standardizing lessons learned from AMP. Parent comment

Re:Standardizing lessons learned from AMP by Ajedi32 on Thursday March 08, 2018 @04:11PM (#16547659)
Fair point, but that problem (at least as far as AMP is concerned) is exactly the one this blog post is addressing: Google is planning to stop pushing AMP specifically in its search results and instead push a set of open web standards which achieve the same technical goals.
[ Parent | on HN ]
Re:Standardizing lessons learned from AMP by beokop on Thursday March 08, 2018 @04:40PM (#16547869)
Even so, I’m tired of jumping through hoops to adhere to bullshit standards that make life hard without any actual benefit. We have HTML and CSS, why do we need AMP? How does my personal webpage benefit from HTTPS? Why did they enforce mandatory HTTPS across the entire .dev TLD in WebKit, breaking my local test env, when it’s only used by a few internal projects at Google?

They seem to have a vested interest in making web development harder than it needs to be.

[ Parent | on HN ]
Re:Standardizing lessons learned from AMP by TheCoelacanth on Friday March 09, 2018 @11:52AM (#16553011)
> How does my personal webpage benefit from HTTPS?

It prevents bad actors like ISPs or public WiFi APs from injecting bullshit into it.

[ Parent | on HN ]
Re:Standardizing lessons learned from AMP by agentdrtran on Thursday March 08, 2018 @05:20PM (#16548239)
> We have HTML and CSS, why do we need AMP?

Do you even know what AMP is?

[ Parent | on HN ]
Re:Standardizing lessons learned from AMP by beokop on Friday March 09, 2018 @12:52AM (#16550034)
Poor phrasing on my part. I meant that fast websites can already be built without adhering to the AMP standard.
[ Parent | on HN ]