3 ms·
One explanation could be that Apple doesn't want an "electron situation," where every app comes with it's own fully-loaded web browser, is a memory and CPU hog,
by gjsman-1000 5y ago
One explanation could be that Apple doesn't want an "electron situation," where every app comes with it's own fully-loaded web browser, is a memory and CPU hog, and a security risk if the app is out of date. Like is currently happening on PCs.
With WebKit, its update once, secure all apps everywhere.
- paulryanrogers 5y agoI'm curious if FirefoxOS had gone differently if Apple and others would've considered supporting a native-web approach for apps. (Albeit also tied to only one or a few blessed HTML and JS engines.)
- JimDabell 5y agoThat was the Apple party line when the iPhone was first released – the only Apple-blessed way to build iPhone applications was to build mobile-friendly web applications. There was a backlash – everybody complained and demanded native applications; the App Store was opened the year after. https://9to5mac.com/2011/10/21/jobs-original-vision-for-the-iphone-no-third-party-native-apps/ https://9to5mac.com/2011/10/21/jobs-original-vision-for-the-...
- paulryanrogers 5y agoIIRC FirefoxOS did it differently. Apps were local bundles of web tech. Not only pinned links to open a browser.