3 ms·

> As far as not giving a shit about Safari's ability to do WebRTC and PWAs properly What's funny here is that many of Google's web initiatives such as PWA and

> As far as not giving a shit about Safari's ability to do WebRTC and PWAs properly What's funny here is that many of Google's web initiatives such as PWA and AMP are at least partially constructed to increase Google's dominance and selling of ads. It's hard to fault any company that pushes against newer web standards and "progress" since it is so slanted in their competitors favor. If you're a Google employee working on some such project you can probably convince me that the majority of the reasoning for PWA/AMP/etc are good, and assessed in its totality it is probably for the greater good, but you'll never convince me the mangers/directors/executives at the budgeting level of these projects are too dumb to understand and latter extract immense value at the expense of users as a final result. All this stuff is too reminiscent of Facebook's Free basics project masquerading as Democratizing Internet "progress" with cool new features no user actually asked for.

matt4077 7y ago
I don't think they are even hiding their motivation. It's basically why Chrome exists, as well: Google needs the open web to stay competitive with native apps, because they only earn money on the web. There isn't really anything nefarious about that, and at the moment it has the benefit of aligning Google's incentives neatly with users'.
- lonelappde 7y ago
  AMP is about moving a huge portion of web hosting from other hosts to Google.com, while trying to hide that fact from users. Look at the antics Chrome does to hide the actual URL and the originally hosting site.
  - Gigablah 7y ago
    By that logic, Cloudflare is doing the same thing then, and on a larger scale.
Andrex 7y ago
You're lumping in PWAs with AMP and I'm confused why, they are apples and oranges. PWAs are an outgrowth of web best practices and new consortium-ratified technologies. AMP is for Google search on mobile (and a couple other places.) To pull some examples from your comment: > What's funny here is that many of Google's web initiatives such as PWA and AMP are at least partially constructed to increase Google's dominance and selling of ads. It's hard to fault any company that pushes against newer web standards and "progress" since it is so slanted in their competitors favor. 1. PWAs are not a Google initiative. AMP is. 2. Migrating to a PWA doesn't advantage Google vs. its competitors, either in search or the browser world. AMP on the other hand is specifically designed to get sites that adopt it better placement in mobile search. 3. Neither PWAs nor AMP are web standards. PWAs are a set of standards adopted by browser vendors (not just Google.) Vendors implement parts in different orders from other vendors (see the various Apple examples in OP.) AMP is not a web standard -- it is an open-source project governed by Google. Please do not conflate PWAs and AMP.

matt4077 7y ago

I don't think they are even hiding their motivation. It's basically why Chrome exists, as well: Google needs the open web to stay competitive with native apps, because they only earn money on the web. There isn't really anything nefarious about that, and at the moment it has the benefit of aligning Google's incentives neatly with users'.

lonelappde 7y ago
AMP is about moving a huge portion of web hosting from other hosts to Google.com, while trying to hide that fact from users. Look at the antics Chrome does to hide the actual URL and the originally hosting site.
- Gigablah 7y ago
  By that logic, Cloudflare is doing the same thing then, and on a larger scale.

Andrex 7y ago

You're lumping in PWAs with AMP and I'm confused why, they are apples and oranges. PWAs are an outgrowth of web best practices and new consortium-ratified technologies. AMP is for Google search on mobile (and a couple other places.) To pull some examples from your comment: > What's funny here is that many of Google's web initiatives such as PWA and AMP are at least partially constructed to increase Google's dominance and selling of ads. It's hard to fault any company that pushes against newer web standards and "progress" since it is so slanted in their competitors favor. 1. PWAs are not a Google initiative. AMP is. 2. Migrating to a PWA doesn't advantage Google vs. its competitors, either in search or the browser world. AMP on the other hand is specifically designed to get sites that adopt it better placement in mobile search. 3. Neither PWAs nor AMP are web standards. PWAs are a set of standards adopted by browser vendors (not just Google.) Vendors implement parts in different orders from other vendors (see the various Apple examples in OP.) AMP is not a web standard -- it is an open-source project governed by Google. Please do not conflate PWAs and AMP.