Kill Google AMP before it kills the web
theregister.co.uk
Kill Google AMP before it kills the web
1–10 of 489 posts
Re: Kill Google AMP before it kills the web
#2[deleted]
Re: Kill Google AMP before it kills the web
#3In 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.g. those mentioned in the linked article.
Re: Kill Google AMP before it kills the web
#4In 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.
Re: Kill Google AMP before it kills the web
#5In 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.…
> I don't mind the idea of having a more standardised subset web page
We already had this two decades ago: WAP, its contemporaries (i-mode), and its immediate successors (XHTML Mobile Profile).
Re: Kill Google AMP before it kills the web
#6In 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.…
> I don't mind the idea of having a more standardised subset web page We already had this two decades ago: WAP, its contemporaries (i-mode), and its immediate successors (XHTML Mobile Profile).
Except mobile Web adoption in 2002 was poor because of form factor, among other things.
Re: Kill Google AMP before it kills the web
#7"publication independence"? Really? The man who is famous among other things for supporting the most closed ecosystem there is around: iOS, where a single company decides what apps are worth publishing and wish ones doesn't. Or does newspaper publication independence is really that more important than software publication independence. The irony is so clear that it's weird that he didn't even mention it.
That genie is out of the box, when you decided that you didn't mind a company gatekeeping which software you can install on "your" devices you opened that can of worms, the one where any company can gatekeep anything they want as long as it is "convenient" for most people.
Re: Kill Google AMP before it kills the web
#8In 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.…
I didn't realize AMP content was hosted by Google.
Re: Kill Google AMP before it kills the web
#9In 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.
> Google using their search monopoly to create a distribution monopoly is also extremely worrying.
Google is using any means possible to keep the web (html, js, css) relevant in the age of native apps (that includes Facebook app running on Android). If the web stays relevant, the same goes for Google search.
Re: Kill Google AMP before it kills the web
#10"If you don't like the news, go out and make some of your own."
Is anyone working on a competing standard?