11–20 of 489 posts
Earlier quoted context omitted.
> 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.
In 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.…
Considering we're on the precipice of a global authoritarian-populist cycle, there are non-market consequences to such concentration, too.
"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 i…
Well, yes. It really is.
The other criticisms about how it performs on iOS seem truly secondary, they could easily fix them but we're still left with the far bigger issue.
Additionally, criticisms about iOS having a closed ecosystem seem irrelevant to this. An App Store is one thing, but starting down the path of effectively adding "high speed lanes" to the supposedly free web is scary.
"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 i…
Google, by contrast, has a far larger share of the search engine market than Apple has of the mobile device market. That means it's more of a concern by default.
In 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).
Earlier quoted context omitted.
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.