201–210 of 249 posts
Earlier quoted context omitted.
> AMP is my only option of getting de-bloated webpages It isn't, though. Plenty of sites out there are de-bloated, and things like Reader Mode in browsers makes the rest work just fine.
Is this really true - every time I switch to non AMP / non Adblock my eyes bleed. User numbers for AMP and Adblock say at least something about the “fact” that sites are debloated.
Earlier quoted context omitted.
Counterpoint: WE don't live in an ideal world and AMP is my only option of getting de-bloated webpages. I would love if managers and directors would do this themselves and AMP wouldn't be needed, but that's just not the case. I have to choose between downloading some text and images to read an article or load 5MB JavaScript SinglePageApp with tracking, ads, auto playing video's... I know in an ideal world AMP would b…
> AMP is my only option of getting de-bloated webpages How about de-bloating your webpages instead? Seriously, people, come on — just put less cruft in your web pages. Don't load 500 trackers. Say no when the marketing guys come over and tell you to add 10 more. Tell your bosses that marketing is incompetent. Push back and tell people that adding cruft is bad. Please don't bother telling me how it "can't be done". It…
For context so people don't get the wrong idea... I just want to point out that the gp you responded to (apexalpha) wrote "my option" and _he_ (as a web surfer) is not the manager in charge of those other programmers adding in the cruft. In his next sentence he wrote:
>I would love if managers and directors would do this themselves and AMP wouldn't be needed, but that's just not the case.
Earlier quoted context omitted.
> I don't think I've ever seen anyone on HN defend AMP I present to you AMP tech lead: https://news.ycombinator.com/threads?id=cramforce
Haha, even they: https://news.ycombinator.com/item?id=16171735
Earlier quoted context omitted.
> AMP is my only option of getting de-bloated webpages How about de-bloating your webpages instead? Seriously, people, come on — just put less cruft in your web pages. Don't load 500 trackers. Say no when the marketing guys come over and tell you to add 10 more. Tell your bosses that marketing is incompetent. Push back and tell people that adding cruft is bad. Please don't bother telling me how it "can't be done". It…
>How about de-bloating your webpages instead? [...] — just put less cruft in your web pages. Don't load 500 trackers. [...] Tell your bosses that marketing is incompetent. For context so people don't get the wrong idea... I just want to point out that the gp you responded to ( apexalpha ) wrote "my option" and _he_ (as a web surfer) is not the manager in charge of those other programmers adding in the cruft. In his n…
NB. the remaining animated gifs can be stopped on palemoon and I think FX with shift+escape.
You occasionally gets CSS animations but they are pretty rare.
When AMP was introduced I assumed the actual content would be loaded from the canonical URL anyway. This whole in-between caching layer G introduced is very weird. Also, I think what AMP was pitted against--Facebook instant articles--no longer exists, or at least doesn't particularly matter (now that FB is several pivots beyond the whole 'newsfeed is full of articles' stage).
One way to think of AMP is as a solution to "When people click on links from search the pages often load very slowly. Can we make this instant?" Any preloading based solution has to involve caching, because otherwise sites could learn that they had shown up in your search results without you having clicked on then. (Disclosure: I work at Google, not on AMP, and I'm only speaking for myself)
Earlier quoted context omitted.
What websites need to not only regularly preload+prerender other webpages but also webpages outside their trustzone? And when does the performance of half a millisecond matter?
Latency to remote servers isn’t half a millisecond. A click off from google would normally take a second or two to render and be much worse at the p95 page load time. With AMP, this is cut down to tens of milliseconds.
The question isn't what do people normally do. The question is what's possible without Google's help. 200ms click-to-render is not difficult.
Google can get that down to 20ms or whatever with AMP, but for 99.999% of sites, Google's monopoly position is not the thing holding you back from faster loads.
Earlier quoted context omitted.
It may not be obvious to users why their site is broken. Of course, at that stage they may blame the site unless they know why the site appears that way in the first place. But it isn't always obvious how to get to the site from an AMP page.
My point was that "broken" feels like the wrong term. I think the site owner should be blamed if content the user needs is not either on the AMP page or accessible with an easily found link.
Hmm. If AMP participation were voluntary, I would agree, but given how necessary it is to SEO ranking, Google deserves a large portion of any blame for broken content - They do not get a free pass to enforce usage of a protocol, but dodge the consequences of its implementation (which will always involve friction and some breakage).
It's ironic to me that AMP is a problem we all brought upon ourselves, really. It's almost (jokingly) a Prisoner's dilemma [1]. Had no one ever opted into it, it probably would have just been swept under the rug by Google, and a win-win for us all. But since a competitor of yours ( probably ) opted into it to get ahead of you, you now have to opt into it also, to compete and get the same SEO "power juice" it gave the…
Counterpoint: WE don't live in an ideal world and AMP is my only option of getting de-bloated webpages. I would love if managers and directors would do this themselves and AMP wouldn't be needed, but that's just not the case. I have to choose between downloading some text and images to read an article or load 5MB JavaScript SinglePageApp with tracking, ads, auto playing video's... I know in an ideal world AMP would b…
Earlier quoted context omitted.
By not having a config item for their search to return the real url. And, as in the main story, the AMP page bricking the link to the real url.
They're working on signed exchanges, you'll soon see the "real URL" of the content.