but that's not really how the world works, and certainly not how Apple works. Executives make hard choices about what to prioritize. This will be one of them.
This is a fundamental misunderstanding of how Apple works. Nobody is debating whether they should keep working on Xcode or Safari; it’s both.
WebKit is one of the most important frameworks Apple makes; many of their own apps rely on it like Mail and the App Store.
And many thousands of 3rd party apps (Facebook, Twitter) rely on WebKit to render web content on macOS, iOS, iPadOS, visionOS and tvOS.
Does losing $18 billion mean some adjustments? Of course, but it’s probably something else that’s not mission critical, not something like Safari/WebKit that’s on over 2 billion devices.
I'm not sure the fact that a web view component exists means it gets priority.
Facebook, Twitter etc have no choice but to use what iOS provides.
It's not like they'd stop publishing iOS apps I'd apple decided to never update the WebView componemt again.
And the audience is captive, if they get a bad rendering in mail they won't think "bad apple" but "bad email sender", same way we all bend around Outlook's rendering.
This is a fundamental misunderstanding of how Apple works. Nobody is debating whether they should keep working on Xcode or Safari; it’s both.
WebKit is one of the most important frameworks Apple makes; many of their own apps rely on it like Mail and the App Store.
And many thousands of 3rd party apps (Facebook, Twitter) rely on WebKit to render web content on macOS, iOS, iPadOS, visionOS and tvOS.
Does losing $18 billion mean some adjustments? Of course, but it’s probably something else that’s not mission critical, not something like Safari/WebKit that’s on over 2 billion devices.