Honestly at this point, if you trust google you’re a fool. It’s demonstrated itself to be unreliable, capricious, and absolutely willing to break the law if it thinks it can get away with it. Do business with them if you absolutely must, but under no circumstance should you actually trust them.
Publishers did not want to have to refactor their page templates with a bunch of AMP markup to please Google. For most companies, it was a question of whether they were OK risking being left behind if other publishers got favourable treatment running stories on AMP validated pages. This comes back to Google's domination of both search and Adwords. And it comes back to the unfortunate reality that people don't want to…
AMP Has Irreparably Damaged Publishers’ Trust in Google-Led Initiatives
131–140 of 172 posts
Re: AMP Has Irreparably Damaged Publishers’ Trust in Google-Led Initiatives
#132As someone mentioned directly in this blog post I can tell you where I came from with the event at least. Trust. Making sure developers know what we're working and why we think it's important and when we can show everyone the data to back up our rationale. I think we still have a long way to go, but it's something I've always strived for my team (devrel) to do. I felt that it was important to ask these questions on t…
Re: AMP Has Irreparably Damaged Publishers’ Trust in Google-Led Initiatives
#133>what he identified as Google’s “vision for the web’s future and examples of best-in-class web experiences.” I'm not sure Google should be the only one to decide the web's future. Since they quasi monopolized the browser, they act like they own the web.
Re: AMP Has Irreparably Damaged Publishers’ Trust in Google-Led Initiatives
#134Earlier quoted context omitted.
This is a narrative (very heavily supported by google btw) that really needs to die. Safari is decidedly neither behind nor as broken as the narrative suggests. Safari ships about as many WebAPIs as Firefox does, and no one blames Firefox to be "behind on standards". More, Firefox is increasingly siding with Safari when deciding not to implement certain Chrome-only "standards". Also see this nice take over at Quirksm…
Safari's slow release cadence (typically tied to OS version upgrades) does leave it more broken and for longer than Firefox, Chrome, Opera and other browsers that are updated more frequently and not tied to the OS. just recently i ran into incompatibilities with Safari https://github.com/leeoniya/uPlot/issues/538#issuecomment-87...
This is true. Apple's inane insistence that everything has to be updated only once a year is truly baffling.
Re: AMP Has Irreparably Damaged Publishers’ Trust in Google-Led Initiatives
#135>Announcements and discussions on hot topics impacting the greater web community at the event included Google’s Privacy Sandbox initiative, improvements to Core Web Vitals and performance tools, and new APIs for Progressive Web Apps (PWAs). Stop trying to make PWAs happen. It's not going to happen.
It's somewhat off topic but why do you say this? Is it the 'progressive' issue or the 'web app' issue. My view is that a browser is a really good way to deliver applications - in fact, I prefer them to any other form of application. I'm not too hung up on the whole 'progressive' thing these days but a NoJS application still has it's benefits.
It's the Google issue. They've been shoving these APIs down our throats trying to make it happen solely to build up the Chrome ecosystem. Firefox does not and will not ever support them, and they will never become an actual web standard, although Google has tried to present it as such.
Re: AMP Has Irreparably Damaged Publishers’ Trust in Google-Led Initiatives
#136Re: AMP Has Irreparably Damaged Publishers’ Trust in Google-Led Initiatives
#137Earlier quoted context omitted.
It's somewhat off topic but why do you say this? Is it the 'progressive' issue or the 'web app' issue. My view is that a browser is a really good way to deliver applications - in fact, I prefer them to any other form of application. I'm not too hung up on the whole 'progressive' thing these days but a NoJS application still has it's benefits.
>It's somewhat off topic but why do you say this? Is it the 'progressive' issue or the 'web app' issue. It's the Google issue. They've been shoving these APIs down our throats trying to make it happen solely to build up the Chrome ecosystem. Firefox does not and will not ever support them, and they will never become an actual web standard, although Google has tried to present it as such.
Re: AMP Has Irreparably Damaged Publishers’ Trust in Google-Led Initiatives
#138Earlier quoted context omitted.
Maybe we should call it MANGA now.
I know you’re joking, but I’m going to oppose that on prudential grounds. I don’t want a form of entertainment I enjoy mixed up with a grouping of companies people are incredibly critical of. Ruins the Google results too.
Edit, oo, I got it: MAANG. That way we can say, "Come on, MAANG!"
Re: AMP Has Irreparably Damaged Publishers’ Trust in Google-Led Initiatives
#139Honestly at this point, if you trust google you’re a fool. It’s demonstrated itself to be unreliable, capricious, and absolutely willing to break the law if it thinks it can get away with it. Do business with them if you absolutely must, but under no circumstance should you actually trust them.
Re: AMP Has Irreparably Damaged Publishers’ Trust in Google-Led Initiatives
#140Earlier quoted context omitted.
During the last antitrust suite against Google it was confirmed that Google developed AMP to combat header bidding in order to protect their price arbitrage cut in their ad exchange. Publishers are now weaponizing against Google.
Isn't the antitrust suite still ongoing? I thought we're still talking of accusations, not proven facts (tho I believe them true).
>249. The speed benefits Google marketed were also at least partly a result of Google’s throttling. Google throttles the load time of non-AMP ads by giving them artificial one-second delays in order to give Google AMP a “nice comparative boost.” Throttling non-AMP ads slows down header bidding, which Google then uses to denigrate header bidding for being too slow. “Header Bidding can often increase latency of web pages and create security flaws when executed incorrectly,” Google falsely claimed. Internally, Google employees grappled with “how to [publicly] justify [Google] making something slower.” [0]
[0] https://storage.courtlistener.com/recap/gov.uscourts.nysd.56...