22 ms·

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 el

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.

JohnFen 7y ago
> 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.
- buboard 7y ago
  > 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
buboard 7y ago
amp is a vehicle to a) turn web content owners to gig writers for google and b) push Signed HTTP Exchanges, a dangerous protocol on the web. I can't attribute stupidity to google because they re very smart, so it must be malice
- squiggleblaz 7y ago
  Why is signed HTTP exchanges dangerous, and indeed, what are they?
  - buboard 7y ago
    https://github.com/ipfs/in-web-browsers/issues/121#issuecomment-489182127 https://github.com/ipfs/in-web-browsers/issues/121#issuecomm... > Google Chome makes SXG indistinguishable from regular HTTPS, which breaks basic assumptions around how users understand the green padlock in location bar (aka "nobody but me and the Origin server can see the payload"). UX of regular HTTPS is reused as-is, pretending that end-to-end HTTPS transport was used with Origin from location bar, which is not true. https://blog.intelx.io/2019/04/15/a-new-type-of-http-client-attacks-is-around-the-corner-and-its-really-sneaky/ https://blog.intelx.io/2019/04/15/a-new-type-of-http-client-... https://docs.google.com/document/d/1ha00dSGKmjoEh2mRiG8FIA5sJ1KihTuZe-AXX1r8P-8/edit https://docs.google.com/document/d/1ha00dSGKmjoEh2mRiG8FIA5s... > Big changes need strong justification and support. This particular change is bigger than most and presents a number of challenges. The increased exposure to security problems and the unknown effects of this on power dynamics is significant enough that we have to regard this as harmful until more information is available.

JohnFen 7y ago

> 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.

buboard 7y ago
> 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

buboard 7y ago

amp is a vehicle to a) turn web content owners to gig writers for google and b) push Signed HTTP Exchanges, a dangerous protocol on the web. I can't attribute stupidity to google because they re very smart, so it must be malice

squiggleblaz 7y ago
Why is signed HTTP exchanges dangerous, and indeed, what are they?
- buboard 7y ago
  https://github.com/ipfs/in-web-browsers/issues/121#issuecomment-489182127 https://github.com/ipfs/in-web-browsers/issues/121#issuecomm... > Google Chome makes SXG indistinguishable from regular HTTPS, which breaks basic assumptions around how users understand the green padlock in location bar (aka "nobody but me and the Origin server can see the payload"). UX of regular HTTPS is reused as-is, pretending that end-to-end HTTPS transport was used with Origin from location bar, which is not true. https://blog.intelx.io/2019/04/15/a-new-type-of-http-client-attacks-is-around-the-corner-and-its-really-sneaky/ https://blog.intelx.io/2019/04/15/a-new-type-of-http-client-... https://docs.google.com/document/d/1ha00dSGKmjoEh2mRiG8FIA5sJ1KihTuZe-AXX1r8P-8/edit https://docs.google.com/document/d/1ha00dSGKmjoEh2mRiG8FIA5s... > Big changes need strong justification and support. This particular change is bigger than most and presents a number of challenges. The increased exposure to security problems and the unknown effects of this on power dynamics is significant enough that we have to regard this as harmful until more information is available.