[moffkalast]

> The need to remove the capability was informed by the complex security and privacy concerns associated with web apps to support alternative browser engines that would require building a new integration architecture that does not currently exist in iOS and iPadOS.

This rationalization makes zero sense, it's just opening a standalone browser window from a convenient icon shortcut. They could even ignore the manifest.json entirely like Android does half the time anyway cause the implementation is buggy as all hell.

I think the real reason was some kind of retaliation worthy of a baby insanity wolf meme because they were forced to stop reskinning Safari for all other browsers on iOS which was absolutely ridiculous in the first place.

[brookst]

Shows why guessing and gut feel are bad basis for opinions.

In fact, Apple’s problem was that the PWA serviceworker runs as root, a bad decision made years ago. Enabling Chrome-hosted PWAs means Google gets root on those peoples’ phones.

We can still lambast Apple and go all ad hom, but let’s stay factual?

[theK]

Sounds like something very fixable though. Why is it so difficult for apple to fix the "engineering mistake" and move the PWA process to a less privileged user or even a jail?

[rejhgadellaa]

Service Workers do not require an installed PWA. Every regular website can have a PWA. I'm not sure who came up with this explanation for Apple trying to kill PWAs in Europe, but it makes zero sense.

[rejhgadellaa]

I meant to say "Every regular website can have a service worker", but can't edit anymore

[moffkalast]

Ok running something like that as root by design is enough of a self own from Apple that I really don't need to say anything more, hahaha

[andrewflnr]

Factual ad hom indeed.

[urbandw311er]

Not doubting you but care to share some links to back this up? I’d be interested to read more.