3 ms·
Feels like the same kind of malicious compliance with the rest of their DMA changes: 1. WebKit has access to special OS-level APIs that allow it to install and
by oddevan 3y ago
Feels like the same kind of malicious compliance with the rest of their DMA changes:
1. WebKit has access to special OS-level APIs that allow it to install and power web apps.
2. The DMA requires support for alternative browser engines with the same abilities as WebKit.
3. It is reasonable to assume this requirement extends to PWAs.
4. By taking away WebKit's ability to power PWAs, all browser engines are now on a level playing field.
_Could_ they have done it differently? Maybe, maybe not: software development always takes longer than you think, and throwing more engineers at a problem doesn't always make it go faster. Do I think they saw another chance to be petulant and took it? Yes.
So yeah, I'm disappointed, but no more here than with the rest of Apple's DMA response.