Re:Standardizing lessons learned from AMP
by themacguffinman on Thursday March 08, 2018 @04:32PM
(#16547804)
You're really missing the broader context here, which was the rise of wholly proprietary news formats like Facebook Articles and Apple News. This was Google's entry into the market that was very much #teamweb vs Facebook and Apple's #teamproprietary because it based itself on open web standards and had a clear pathway towards standardization (that you see materializing in the OP's article).
This was the best solution the web could hope for that balanced open standard concerns with the necessary commercial backing that advantaged AMP's proprietary competitors.
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.
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.
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.
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?
I actually have a lot less issue with AMP as a technological solution, as I do with the Google's "our way or the highway" treatment of the Internet. Google uses both it's search monopoly and it's browser monopoly (and often, both at the same time) to force the entire world to do whatever Google wants them to.
Sometimes you might perceive the result to be "good", but that doesn't justify the behavior. That's why another technical implementation change blog doesn't improve anyone's mood about the whole thing: Because Malte Ubl is still pretending he's on #teamweb and not #teamgoogle.