...If iOS 13 were to add mouse support could we see an ARM based touch screen iOSBook running iOS with ports of some MacOS applications to follow?
Apple owns the trademark to 'iBook'. Prune out the "OS" out of iOSBook and ta-da. A name they already own.
It would also fit with the vision of converging OS’s and moving to ARM.
Next weeks WWDC should make it more clear but Apple probably isn't converging the OS's as much as they are on a 1-2 year path to converge the AppStores. Developers will compose an application bundle that can adapt to various OS platforms and "thin" itself on deployment from the AppStore. So if download to an iPhone then you get the iPhone subset of the app. Download to a Mac and you get the Mac app resources subset.
From the end user perspective of bought once deploy where they want it is the "merged OS", but underneath it will be a slightly different story. ( nor will the feature set be 100% the same everywhere on each app. )
If they do that it will be easier to split the macOS coverage into part ARM ( lower 'half' of laptop line up and perhaps grow that over time) and part x86 (desktops and shrink the upper "half" of the laptop line up over time). In short, no "big bang" switch over of Mac CPU.
Apple sells relatively expensive keyboards with iPad Pro ( and iPads) so iOS (at least the subset for the iPad line up) can't just be pure touch only. Touchpad (vs mouse focused ) support may only overlap. iOS for iPad Pro is going to expand but that doesn't mean it is going to grow to subsume all of macOS feature set. (that end goal is 'merge' as opposed to being 'more useful' with set of hardware add ons it is sold with. )
I may be just dreaming but Apple under Jobs always seemed to wow us.
I suspect the 'Wow' is going to be automagically context adapting application GUIs that change to be most useful on the platform you are on. From the outside it will look like "Write once, run anywhere with not sacrifices in looking 'good' ". Under the covers where the developers are it won't be 100% magical. They will be work to do, but Apple is going to try to make it "somewhat easy" to do ( so that more folks do it).
Super good autolayout has been a Holy Grail objective for lots of years. If Apple gets pretty close that will be a 'Wow'.
The iPad Pro already have storage surpassing the MacBook 12. If they are going to move off Intel the MacBook 12 seems like the most appropriate Mac to do it with.
The problem is if that is the only Mac they flip to ARM how does the macOS software ecosystem work? If they keep the binaries separate for a longer period of time how do folks react to their legacy apps and keeping track of which copy goes where.
But yes... tossing the A-series processor that they are doing for the iPad Pro anyway into a MacBook 'container' shouldn't be that hard. Especially if they both have exactly one port that implements the same socket type and implementation. The MacBook and the iPad Pro have been largely coupled all along.
[doublepost=1559328632][/doublepost]
The vision of converging OSs is a fantasy that will never happen. Craig F. said.
Merging versus converging are a subtle difference. iOS and macOS share a basic kernel (Mach). Same HFS+ and now APFS. Same Metal for graphics stack. That's isn't really a "convergence" or a "merge" since they have been 'shared" all along.
What has crept in are some 'forks' where the development on iOS has added a subset of stuff that Apple didn't fold back into the common subset. For example, HFS+ added a bunch of smaller features that macOS never got. As that HFS+ fork drifted more apart from the mainline, Apple decided to do APFS so that could 'undo' the drift apart and get a more modern filesystem (oriented toward being SSD everywhere. ). Labeling that "fork undo" as convergence is appropriate.
The notion that lots of folks have spread is that Apple is trying to completely merge iOS and macOS into one single OS line of development. "One OS to rule them all". That's seems to be 'No' as they have said. They aren't looking to remove all the differences. Nor looking to put everything into one overly complicated pile. But they also aren't looking to keeping them maximally different either. Sharing major components like the kernel , file systems , etc helps keeps costs and maintenance overhead down. You don't have to 'fix' multiple forked version 2-4 times. Less time spent porting to different code forks means can they can spend more time on fixing more issues (as opposed to 4 variations of the same issue. [ there are always more bugs and new feature requests than there are developers available. ]
Same for tvOS , watchOS . Some subset different, but not wholly different.
Making them so different that developers can't deploy to all four OS without "painful" effort is bad for the whole ecosystem ( especially when there is some baseline commonly present). Apple is probably moving to make that "easier". That is only a merge/convergence of possibly the AppStore not necessarily the operating systems.
[doublepost=1559329437][/doublepost]
Would buy that the moment they announced it.
Macbook chassis, ARM, LTE, Apple's productivity suite + normal file
system. Bonus points for touchscreen and FaceID.
Unbeatable combo.
Problem is - that would seriously cut into Macbook Pro sales.
For those who have either high amounts of legacy macOS apps , virtual machine workload ( Windows, Linux , etc) , and "heavy lifting" performance there wouldn't be much of a dent in MBP sales.
Folks who get 98+% of their apps from the AppStore, run a single macOS instance all the time, and need always on connection with max mobile size and weight then yes. But not sure that should have been a core MBP sales market in the first place.
Thinnest at all costs also has chance that it screws up LTE. Where will the antennas go? It is doable if they back off of weight slightly, but the mania requirement on reducing weight gets in the way.
P.S. the Macbook would probably have problems with FaceID. The quest to make it as light as possible compromised room for a camera ( which is why it distinctly trails the resolution of the newer design for MBA and MBP in resolution. If trowing resolution out the window to strip weight.... FaceID isn't going to work. It is actually an even bigger camera subsystem.
Nor is Apple likely to put a touchscreen on it with macOS. iOS for iPad Pro and a 360 2-in-1 hinge so that the OS was touch skewed (an iPad with a keyboard permanently attached) perhaps, but not with macOS.