122
you are viewing a single comment's thread
view the rest of the comments
[-] dpkonofa@lemmy.world -1 points 10 months ago* (last edited 10 months ago)

That’s not true, though. The way that PWAs render and run is different from the way they run inside of an app like a browser. Because they were required to allow different browser engines, it seems Apple initially thought that meant they needed to allow PWAs to run via different engines too, hence the initial stance. Based on the law, as written, It’s completely reasonable for them to interpret it that way. Since that’s not the case, they’re not changing the current PWA implementation.

[-] rmuk@feddit.uk 8 points 10 months ago

Apple was trying to get rid of PWAs. End of. If you used Safari: no PWAs. If you use Firefox or Edge: no PWAs. Since the PWA rendering engine is part of the OS in the same way that MacOS and Windows include their own web rendering engines separate from the web browsers, they could easily continue use that for PWAs even if Safari was 'uninstalled'. The whole thing was Apple throwing a tantrum at being forced to do something for the benefit of not-Apple.

this post was submitted on 01 Mar 2024
122 points (98.4% liked)

Apple

17607 readers
28 users here now

Welcome

to the largest Apple community on Lemmy. This is the place where we talk about everything Apple, from iOS to the exciting upcoming Apple Vision Pro. Feel free to join the discussion!

Rules:
  1. No NSFW Content
  2. No Hate Speech or Personal Attacks
  3. No Ads / Spamming
    Self promotion is only allowed in the pinned monthly thread

Lemmy Code of Conduct

Communities of Interest:

Apple Hardware
Apple TV
Apple Watch
iPad
iPhone
Mac
Vintage Apple

Apple Software
iOS
iPadOS
macOS
tvOS
watchOS
Shortcuts
Xcode

Community banner courtesy of u/Antsomnia.

founded 2 years ago
MODERATORS