3 ms·
This article doesn't address any of the reasons people have issues with AMP. All it confirms is what we already know: That Google gives preferential treatment t
by ocdtrekkie 9y ago
This article doesn't address any of the reasons people have issues with AMP. All it confirms is what we already know: That Google gives preferential treatment to sites which use their products and services.
And, like many engineering blogs about employing Google products, seems like it might've been suggested by a Google marketing team.
- donohoe 9y agoNo, in most companies the engineers do not write posts because someone from another company reaches out to the marketing team at that company.... developers don't like that and besides, Oscar is a good guy.
- oscrperez 9y agoFor real... Tnx!
- oscrperez 9y agoThis post is not meant to be a critical piece addressing the issues people have with AMP. That's not the goal here. The goal is to show the reason why we serve AMP content and the tech behind it. There's a lot of conspiracy theories and misunderstanding about how AMP works in the community. AMP is by no means perfect, but its dangers are greatly exaggerated. If you don't trust Google's CDN, no one is forcing you to use Google. The benefits for non-tech users (e.g. my cousin in a 3rd world country with a 2G connection) are there and are clear.
- ocdtrekkie 9y agoActually, Google is forcing you to use Google. Because your search rankings are dependent on Google getting to cache your content on Google's CDN. There is no situation where you can have your content only cached on someone else's CDN, and get all of the borderline illegal perks of Google favoring content stored on their servers.