Earlier quoted context omitted.
> I've been tracking their GitHub and what is happening is that while yes, the source is open, they won't let you add anything they don't like. Well, thats basically how Android works. And with the upcoming policy changes (in CDD and GCM) things will get even worse.
Could you tell me about those changes?
The Problem with AMP
341–350 of 353 posts
Re: The Problem with AMP
#342Earlier quoted context omitted.
Firefox has 'reading mode' that does similar, strips out all the stuff such as sidebars, etc, without most of the downside associated with AMP (being open, to start with). Occasionally it misses some media stuff (e.g. embedded videos), but works well vast majority of the time so I'm happy with it.
Makes me sad that they pushed AMP vs creating a standard format for how 'reading mode' content is selected. This probably would speed up loading times as it would only have to display/load certain content. I love 'reading mode' on firefox and safari (mobile). Unsure what other browsers support it but they all should.
Re: The Problem with AMP
#343Earlier quoted context omitted.
I'm an individual, not a company. I make web pages. Lots of other individuals also make web pages. It's not like only companies make websites and consumers only use websites.
I'm pretty sure the number of individual web devs is vastly lower than the number of consumers.
Re: The Problem with AMP
#344Earlier quoted context omitted.
Prople in my family get quite confused when trying to share links.
This is my main problem with it. I don't mind too much that it loads an AMP page (well, I don't know, I go back and forth on it), it's the fact that if I want to share the page afterwards, I want the page to be shared to be the original site, not the AMP site, and finding a non-AMP version of the link is damn near impossible.
Check the link rel canonical tag. Obviously not ideal but nowhere near "impossible"
Re: The Problem with AMP
#345Earlier quoted context omitted.
> The open solution to a faster mobile web would have been so easy: Just penalize large and slow web pages without defining a dedicated mobile specification It's obvious they have a different view on this. You can see this first-hand on their pagespeed tool. Pagespeed ranks your pages mostly according to random features, irregardless of size and performance. Actual test you can perform: 1kb web page with no compressi…
>You can taste that this has spread into google monoculture by the performance of their own web services. I gave up on Google Maps a long time ago. On my desktop or laptop, it loads in chunks . Like, the map loads, then the search bar loads, then the navigation (zoom tools, etc) loads. When I click and drag, many times I end up selecting the page instead of moving the map because it hasn't finished loading. I use Bin…
Re: The Problem with AMP
#346Earlier quoted context omitted.
> They are a business, doing exactly what they are supposed to be doing. There was such a thing as ethical and societal responsibility for businesses. Thinking making profit by any means as long as they are nominally legal is acceptable for a company is just something some people believe. No natural law that says it has to be so -- we could easily (and have had) believe the opposite.
>There was such a thing as ethical and societal responsibility for businesses. Since when? Standard oil? Or going back further, the Dutch East India Company?
Which goes back all the way to ancient Babylon in some form or another. There are countless instances in history of shady businessmen being taken to trial or punished by an angry mob.
(And the "Dutch East India Company" was accountable to its society -- and even nationalized at some point. It just exploited OTHER societies and countries).
Re: The Problem with AMP
#347Earlier quoted context omitted.
Could you tell me about those changes?
I am under NDA so I cant give you specifics but the general theme of the changes are: less power to manufacturers, more to carriers.
What about the owners of the phones? I pay money — good money, quite a bit of it — for my phone. I own it. It should do exactly what I want, not what Google, Apple, Samsung, Sprint, Verizon or T-Mobile want.
Re: The Problem with AMP
#348Yeah you can use Cloudflare to serve amp from your own subdomain instead of Google's CDN. https://blog.cloudflare.com/accelerated-mobile/
Not within google search results though.
"Cloudflare now powers the only compliant non-Google AMP cache with all the same performance and security benefits as Google."
https://blog.cloudflare.com/accelerated-mobile/
The term "compliant" would make it seems as though Google has them as a trusted source now and as such will show that content in AMP features in Google
Re: The Problem with AMP
#349Earlier quoted context omitted.
I am under NDA so I cant give you specifics but the general theme of the changes are: less power to manufacturers, more to carriers.
> less power to manufacturers, more to carriers. What about the owners of the phones? I pay money — good money, quite a bit of it — for my phone. I own it. It should do exactly what I want, not what Google, Apple, Samsung, Sprint, Verizon or T-Mobile want.
Re: The Problem with AMP
#350Earlier quoted context omitted.
>You can taste that this has spread into google monoculture by the performance of their own web services. I gave up on Google Maps a long time ago. On my desktop or laptop, it loads in chunks . Like, the map loads, then the search bar loads, then the navigation (zoom tools, etc) loads. When I click and drag, many times I end up selecting the page instead of moving the map because it hasn't finished loading. I use Bin…
They have a "google maps lite version" that loads a little faster, because it misses a bunch us useless crap, but looks 90% the same. It feels somewhat faster.