Tim Cook recently made some comments about the fusi of iOS and macOS. It may have been misunderstood. Let's See Where It All Goes
In December, Mark Gurman at Bloomberg Technology wrote: "Apple is planning iPhone, iPad and Mac applicatis to create a user experience." An internal Apple project called "Marzipan".
The UNIX power of macOS is a sacred foundati for many people.
This involves unifying the code base and APIs of iOS and macOS. Relative ease:
… design a unique applicati that works with a touch screen or a mouse and trackpad depending whether it works the iPhone or iPad operating system or Mac hardware, according to people close to the subject.
This is a big problem because if iOS is a fork of macOS, its own frameworks and APIs have evolved over time to meet the unique needs of iPads and iPhones, including ARM processors. By synchrizing them, developers can write ce and deploy to platforms, targeting Intel or ARM. (Maybe, e day, ly ARM.) That's why Apple is pushing to do all 64-bit macOS applicatis. iOS apps are already.
The impact will be huge. Author Gurman Notes:
Developers currently have to design two different applicatis – e for iOS, the operating system of Apple's mobile devices, and e for macOS, the system that runs Macs. It's a lot more work. What's more, Apple customers have lg complained that some Mac applicatis are not lagging behind. For example, while the Twitter app for iPhone and iPad is regularly updated with the latest features of the social network, the Mac versi has not been updated recently and is widely regarded as substandard. With a single applicati for all machines, Mac, iPad and iPhone users will benefit from new features and updates at the same time.
Running iOS applicatis a Mac would be useful. 19659013] The comm basis of applicati does not mean a formal fusi of OS
Under the hood, however, iOS and macOS have different compents. macOS is …