AMP: the missing controversy
ferdychristant.com
AMP: the missing controversy
1–10 of 143 posts
Re: AMP: the missing controversy
#2We were discussing with the AMP project tech lead over on GitHub trying to suss out details about governance and the like, and it's even scarier than we thought when it came to AMP4Email: Gmail is implementing AMP in email "the way they want to", and AMP Project is just deciding whether or not they want to support it/publish a 'standard'.
I strongly recommend this for reading: https://github.com/ampproject/amphtml/issues/13597 (locked, sadly) and the original AMP4Email issue has a fair bit as well: https://github.com/ampproject/amphtml/issues/13457 (only for discussion of email).
Unfortunately, there are lots of people talking about how bad AMP is, and why, but nobody yet has suggested how we do anything to stop it.
Re: AMP: the missing controversy
#3We were discussing with the AMP project tech lead over on GitHub trying to suss out details about governance and the like, and it's even scarier than we thought when it came to AMP4Email: Gmail is implementing AMP in email "the way they want to", and AMP Project is just deciding whether or not they want to support it/publish a 'standard'. I strongly recommend this for reading: https://github.com/ampproject/amphtml/is…
I think the best thing to do is just be the kind of online citizen you want to see. It may be small but it is something you can do yourself.
I will be looking for a way to move my online identity away from Google to something I control more directly. I am also going to try replacing my social media activity with email. The web is already decentralized, we just need to use it.
Re: AMP: the missing controversy
#4We were discussing with the AMP project tech lead over on GitHub trying to suss out details about governance and the like, and it's even scarier than we thought when it came to AMP4Email: Gmail is implementing AMP in email "the way they want to", and AMP Project is just deciding whether or not they want to support it/publish a 'standard'. I strongly recommend this for reading: https://github.com/ampproject/amphtml/is…
Another issue that raises the same questions is closed and locked: https://github.com/ampproject/amphtml/issues/13623
From the issue:
> I think that the conversation itself is important and I'm always available on the internets.
cramforce is https://twitter.com/cramforce
Re: AMP: the missing controversy
#5We were discussing with the AMP project tech lead over on GitHub trying to suss out details about governance and the like, and it's even scarier than we thought when it came to AMP4Email: Gmail is implementing AMP in email "the way they want to", and AMP Project is just deciding whether or not they want to support it/publish a 'standard'. I strongly recommend this for reading: https://github.com/ampproject/amphtml/is…
Another issue that raises the same questions is closed and locked: https://github.com/ampproject/amphtml/issues/13623 From the issue: > I think that the conversation itself is important and I'm always available on the internets. cramforce is https://twitter.com/cramforce
I'm also kinda trying to keep the issue alive here: https://github.com/ampproject/amphtml/issues/13600
Re: AMP: the missing controversy
#6We were discussing with the AMP project tech lead over on GitHub trying to suss out details about governance and the like, and it's even scarier than we thought when it came to AMP4Email: Gmail is implementing AMP in email "the way they want to", and AMP Project is just deciding whether or not they want to support it/publish a 'standard'. I strongly recommend this for reading: https://github.com/ampproject/amphtml/is…
I think we have to participate.
It claims to be an open standard; we should participate (or try to participate) in the open standard.
The problems AMP solves are real. They will be solved one way or another. I'm hopeful they can be solved in an HTMLite sort of way, not a whatever-Google-does sort of way.
So let's think about how to improve AMP, change AMP, evolve AMP, until it becomes something else and something better than even its creators thought. Destroy it from the the inside.
EDIT: I know AMP has been terribly approached, and it might be nice if it just disappeared. I'm not claiming otherwise. But it's not going to disappear the same way proprietary LiveScript didn't disappear. I don't want to just scream at walls; we've been trying that.
Re: AMP: the missing controversy
#7You can add a controversy to the new controversy presented in the article, because even that conditional speed improvement only happens if you ignore the rest of the environment. Meaning, it will be significant if the user is arriving from google search and only focused on browsing.
If the user has GPS consuming 3G data, or some other app they care about, and only did a quick google search to confirm something, now the GPS or other app data will be severely limited while the browser download all that crap about some 20 different sites the user will never ever visit.
I personally disable preloading on everything, because waiting 3s for a page to show up is a very fine tradeoff to control what my device is downloading and when.
Re: AMP: the missing controversy
#8You can add a controversy to the new controversy presented in the article, because even that conditional speed improvement only happens if you ignore the rest of the environment. Meaning, it will be significant if the user is arriving from google search and only focused on browsing. If the user has GPS consuming 3G data, or some other app they care about, and only did a quick google search to confirm something, now t…
How does one deactivate the amp preloading?
Re: AMP: the missing controversy
#9We were discussing with the AMP project tech lead over on GitHub trying to suss out details about governance and the like, and it's even scarier than we thought when it came to AMP4Email: Gmail is implementing AMP in email "the way they want to", and AMP Project is just deciding whether or not they want to support it/publish a 'standard'. I strongly recommend this for reading: https://github.com/ampproject/amphtml/is…
I think we have to participate. It claims to be an open standard; we should participate (or try to participate) in the open standard. The problems AMP solves are real. They will be solved one way or another. I'm hopeful they can be solved in an HTMLite sort of way, not a whatever-Google-does sort of way. So let's think about how to improve AMP, change AMP, evolve AMP, until it becomes something else and something bet…
The best way to improve AMP is to drag it out behind the wood shed and shoot it. People just need to get better at making mobile web pages.
Re: AMP: the missing controversy
#10You can add a controversy to the new controversy presented in the article, because even that conditional speed improvement only happens if you ignore the rest of the environment. Meaning, it will be significant if the user is arriving from google search and only focused on browsing. If the user has GPS consuming 3G data, or some other app they care about, and only did a quick google search to confirm something, now t…
How does one deactivate the amp preloading?
Use a different search engine.