Earlier quoted context omitted.
Without their monopoly search position no one would be forced to adopt amp and further strengthen said monopoly position.
> Without their monopoly search position no one would be forced to adopt amp It is used by the major search engines in every major market, so yes, they would be forced to adopt AMP. Compare to Apple News, which gives the publisher even less control. Once again, how is it abusing their monopoly position if all their competitors get to benefit from it for free? Finally, how do you propose to enable safe prerendering on…
How to fight back against Google AMP as a web user and a web developer
431–440 of 570 posts
Re: How to fight back against Google AMP as a web user and a web developer
#432It's funny that, if it was a net neutrality issue, e.g. Comcast pushing a new video format and prioritizing video for their own streaming service, the internet would be a warzone by now. But we all love google. And google used to be all fuzzy and unevil. But now they 're evil
How can anyone categorize AMP as evil? They are improving and leading. No one needs to use Google, they have alternatives. This is how things evolve. Someone else will create another amp alternative and things will change later. Netflix was #1, then Hulu, Disney, amazon video came. No one lasts forever, everyone needs to evolve and this exactly is what google is doing.
"Evil" is not a word I'd use. I think AMP is bad for numerous reasons, most of which are detailed in other comments. But the reason that is most relevant to your comment is that AMP makes the web experience worse for me.
> Someone else will create another amp alternative
Yes, I fear that this will happen.
Re: How to fight back against Google AMP as a web user and a web developer
#433It's funny that, if it was a net neutrality issue, e.g. Comcast pushing a new video format and prioritizing video for their own streaming service, the internet would be a warzone by now. But we all love google. And google used to be all fuzzy and unevil. But now they 're evil
How can anyone categorize AMP as evil? They are improving and leading. No one needs to use Google, they have alternatives. This is how things evolve. Someone else will create another amp alternative and things will change later. Netflix was #1, then Hulu, Disney, amazon video came. No one lasts forever, everyone needs to evolve and this exactly is what google is doing.
Re: How to fight back against Google AMP as a web user and a web developer
#434Earlier quoted context omitted.
Stop hoarding tabs. Anyway I think those are arguments in the past anyway.
"In the past"? I can reproduce this on my daily driver today . Why do I need to change my workflow because Firefox got worse at what I've used it for for years? If I have to change the way I work, why not change browsers too? If there's a tab limit beyond which Firefox can't effectively control itself, why is that not a hard coded limit?
Re: How to fight back against Google AMP as a web user and a web developer
#435Earlier quoted context omitted.
How can anyone categorize AMP as evil? They are improving and leading. No one needs to use Google, they have alternatives. This is how things evolve. Someone else will create another amp alternative and things will change later. Netflix was #1, then Hulu, Disney, amazon video came. No one lasts forever, everyone needs to evolve and this exactly is what google is doing.
> How can anyone categorize AMP as evil? "Evil" is not a word I'd use. I think AMP is bad for numerous reasons, most of which are detailed in other comments. But the reason that is most relevant to your comment is that AMP makes the web experience worse for me. > Someone else will create another amp alternative Yes, I fear that this will happen.
nobody showed an interest in making mobile websites fast even though they ve been slow for years. The whole javascript corporate ecosystem is still openly pushing heavy javascript apps even though sites are mobile-first today. only google cared
Re: How to fight back against Google AMP as a web user and a web developer
#436Earlier quoted context omitted.
This doesn't address those problems, it has effectively created a second, proprietary web which is only accessible from the Google home page. If Google actually wanted to improve the web, they wouldn't be splintering it, they would reward publishers with better search placement for building user-friendly sites. As it is, AMP is little more than a way to ensure the "Google" web is better than the non-Google web. Which…
AMP pages are just HTML. Publishers can and do use AMP pages as their "regular" pages that every user sees, not just those coming from Google. Other aggregators (Bing, Twitter, LinkedIn, etc) link to AMP versions. These pages are far from only accessible from Google queries.
Re: How to fight back against Google AMP as a web user and a web developer
#437Earlier quoted context omitted.
The 8-second delay is there to punish users who block JavaScript that is loaded from Google's servers (with ad-blockers) but still have JavaScript enabled.
I think that's a bit unnecessarily tin-foil-hat. If they didn't put in the 8 second css rule it would just show blank for those users right? So adding that rule is making it work at all instead which doesn't sound like "there to punish them".
Re: How to fight back against Google AMP as a web user and a web developer
#438I worked on amp for a leading newspaper, and everyone who says that amp is about "making the web faster on mobile" is either very naive or doing marketing for google. For publishers, amp is about trying to top the results on google search and capture traffic, it's their only motivation to publish their content using amp, and the only metric they look in order to evaluate the results. Once they have their amp content,…
Serious question: what else those websites are supposed to do (that AMP does not provide) with all those megabytes of scripts? Newspapers display a text and an image and very rarely an interactive content(Election day maps and charts, mostly). Is there a reason FROM USERS PERSPECTIVE to have different website codebase for each publisher? For years the Web community kept creating new JavaScript libraries every day and…
No, the alternative is quickly skimming low-quality content with an adblocker and reader mode.
Re: How to fight back against Google AMP as a web user and a web developer
#439Earlier quoted context omitted.
Higher rankings and google will preload the amp page they have and their servers for the amp link. That's why it is a tiny bit faster. It has nothing to do with the amp spec itself. It's faster because google is abusing it's monopoly search position to pre-load.
> google is abusing it's monopoly search position to pre-load. How is that abusing their monopoly search position? Abusing their monopoly search position would be making publishers integrate directly with them to enable preload, like Apple News. Instead, they ask publishers to serve documents that can safely be prerendered, and all their competitors get to (and do!) consume those documents as well to enable safe prer…
Re: How to fight back against Google AMP as a web user and a web developer
#440Earlier quoted context omitted.
> They load massively faster than normal sites, especially on poor mobile connections where main sites sometimes hang indefinitely trying to load javascript, ads, etc. Have you tried the normal mobile websites with an adblocker?
Good luck doing it on mobile phone. I'd say 99.99% users out there on mobile never even attempted to use another browser than safari or chrome for ios.
Whether or not people actually install them is a good question, though.