With respect to scrolling: We (AMP team) filed a bug with Apple about that (we didn't implement scrolling ourselves, just use a div with overflow). We asked to make the scroll inertia for that case the same as the normal scrolling. Apple's response was (surprisingly) to make the default scrolling like the overflow scrolling. So, with the next Safari release all pages will scroll like AMP pages. Hope Gruber is happy t…
Kill Google AMP before it kills the web
371–380 of 489 posts
Re: Kill Google AMP before it kills the web
#372With respect to scrolling: We (AMP team) filed a bug with Apple about that (we didn't implement scrolling ourselves, just use a div with overflow). We asked to make the scroll inertia for that case the same as the normal scrolling. Apple's response was (surprisingly) to make the default scrolling like the overflow scrolling. So, with the next Safari release all pages will scroll like AMP pages. Hope Gruber is happy t…
On top of this: we currently have a team working to fix webkit bugs that are problematic for AMP. This, of course, will make webkit better for everyone.
Re: Kill Google AMP before it kills the web
#373Earlier quoted context omitted.
Do ad blockers really solve the problems that this article criticizes AMP for? You've closed one bag of worms and opened another one. How can independent publishers live in an all adblock world? State publishers like criticized in the article might survive. You're again centralizing journalism, this time into the few organizations that can get their readers to pay a subscription.
I think that the ones that will best survive in an ad-blocking world would be hobbyist journalists and bloggers. That does not seem to be that bad to be quite frank as it would probably lead to higher quality content, less copy-paste and less clickbaits.
Re: Kill Google AMP before it kills the web
#374Earlier quoted context omitted.
It isn't related to iframes directly. Iframes in mobile Safari are never scrollable. The div thing you suggest would have the same issue. If you are a web developer you likely have built a website that has this issue.
Ah. I mostly do back end work, the front and stuff I do we haven't spent any time on optimizing it for mobile, only desktop browsers. I'm not familiar with the quirks of mobile browsers. I only know the iframes scroll oddly because I've been told that was why AMP pages feel weird on iOS here on hacker news before.
Re: Kill Google AMP before it kills the web
#375Earlier quoted context omitted.
Such a solution has existed for at least a decade: ad blocker :)
Do ad blockers really solve the problems that this article criticizes AMP for? You've closed one bag of worms and opened another one. How can independent publishers live in an all adblock world? State publishers like criticized in the article might survive. You're again centralizing journalism, this time into the few organizations that can get their readers to pay a subscription.
We outsourced our opinions and fact-finding to journalists for a few hundred years. Now that time has past. Journalists themselves have destroyed their own industry by producing a poor quality product. Maybe in future journalists will re-invent themselves as purveyors of pure factual reporting, and those that care about that kind of thing will pay for it. But it is a niche market. Democracy, decency, enlightenment and society will suffer of course. But those things were never guaranteed with any kind of real safeguards.
Re: Kill Google AMP before it kills the web
#376Ive forced myself to use Bing since google introduced AMP. Do I like it better than Google? No, I don't. But! I like not having google become my single source of content more than I dislike the slight drop in quality as a result of using Bing. I like the sites I go to, to have control over their content and being able to easily link to them. I think it's reprehensible for google to push this so relentlessly and beyon…
The internet is going to be all AMP and PWA soon, so everything is served from google or on the app store. Enjoy! /barf.
Re: Kill Google AMP before it kills the web
#377Re: Kill Google AMP before it kills the web
#378Earlier quoted context omitted.
> I don't think they're actually are a lot of Apple fan is claiming that the one benevolent company should control everything as you posited earlier your post. Not of course directly, as that would sound obviously fanatical, but the walled garden is almost universally cited as the "best thing" about iOS compared to more open platforms like Android. This recent article in MacWorld invokes it at least five times, sayin…
> But from 3rd party developer's perspective, I can assure the more open platform is better. I'm not sure that follows. But anyway, if being more open is a good thing then Google purposefully trying to shove everyone into their various products and ecosystems seems precisely the opposite of "open" to me. I was never really a big fan of chrome but when you Google released it and the web started getting a lot better th…
Re: Kill Google AMP before it kills the web
#379Earlier quoted context omitted.
> I don't think they're actually are a lot of Apple fan is claiming that the one benevolent company should control everything as you posited earlier your post. Not of course directly, as that would sound obviously fanatical, but the walled garden is almost universally cited as the "best thing" about iOS compared to more open platforms like Android. This recent article in MacWorld invokes it at least five times, sayin…
> But from 3rd party developer's perspective, I can assure the more open platform is better. I'm not sure that follows. But anyway, if being more open is a good thing then Google purposefully trying to shove everyone into their various products and ecosystems seems precisely the opposite of "open" to me. I was never really a big fan of chrome but when you Google released it and the web started getting a lot better th…
Re: Kill Google AMP before it kills the web
#380In theory* I don't mind the idea of having a more standardised subset web page that has a consistent internal structure and that renders quickly. However, having Google load this structured content and host it on its own platform is a terrible idea. Content should remain on the publisher's site. Putting too much content in one place is dangerous for competition. * In practice there are implementation problems too, e.…
Google using their search monopoly to create a distribution monopoly is also extremely worrying.