The argument with which Apple apologists seek to defend the Webkit engine monopoly is that Chrome and other browsers based on the Chromium engine would otherwise take over and turn the web into a Browser monoculture. Apple would have plenty of resources–and resource allocation is at the heart of Alex Russell’s concerns–to compete on the merits. It’s just more profitable and more comfortable to abuse a typical aftermarket monopoly.

The suggestion that a browser monoculture on iOS is needed to prevent a browser monoculture on the Internet as a whole is a “fight fire with fire” argument. Apple is the gatekeeper standing between the technology industry at large and one billion users–by some describes as the world’s richest billion people, which is not completely off base, though fortunately even some rich people prefer Android.

Far be it from me to deny that the concentration of power in Google’s hands with its search engine, ad network, Android, and Chrome raises concerns. However, apart from Android, where Google leverages the Power of Default, Chrome actually managed to compete on the merits. OK, some antitrust enforcement accelerated its adoption–but that’s precisely what is needed against Apple’s single-browser-engine policy now.

The 2020 United States et al. v. Google antitrust complaint mentions Chrome, but only in contexts where Google leverages its power over Chrome to maintain its search engine monopoly. Only on Android does Google leverage its market power in another field to strengthen Chrome.

If you let Apple and Google compete on the merits, such as on Windows where neither Apple nor Google benefits from the Power of Default or simply disallows competition, Google will win. Safari never made it big on Windows, while Chrome did.

Alex Russell is right that “Apple has foundationally imperilled the web ecosystem by destroying the utility of a diverse population of browsers and engines.” And CNET’s Stephen Shankland interestingly noted that web developers are asking lots of questions about where Apple stands on new web standards, i.e., whether and how WebKit will implement them:

One data point related to @slightlylate‘s (newest) post complaining Apple is hurting the web: I follow browser mailing lists, and a large fraction of the Webkit messages are browser devs requesting Apple’s stance on dozens of new web standards. https://t.co/e3SJJoaZHR pic.twitter.com/uyrDBPcVF8

— Stephen Shankland (@stshank) June 27, 2022

In closing, just like Alex Russell, let me, too, amplify Stuart Langridge’s call to “help the [UK] CMA help the Web” by providing input to the CMA (deadline: July 22).

Follow @FOSSpatents

Share with other professionals via LinkedIn:

The post Anti-innovative effects of Apple’s Orwellian prohibition of alternative browser engines finally being discussed and investigated appeared first on Rocky Mountain Patent.