Shared publicly  - 
In four years or less, there will not be iOS and OS X. There will be just one Apple operating system that works across all of its devices.
Chris Robato's profile photoChris Cho's profile photoPaul Osuch's profile photoNick Chamberlain's profile photo
I agree with you, and I hate it hate it hate it. I was already investing a lot of personal time exploring HTML5 on the iPhone so developers could break free from the iOS App Store; now it looks like my research will be just as relevant to the Mac desktop in a few years.
Intel vs ARM will be a big challenge to make that a reality. Personally don't see it happening but they sure are looking to make them feel the same. 
+Jason Ehle is right- that will never happen (not at least till power and cooling technology evolves so much it'll actually be practical). I'm sure memory handling is very different and there's great difference what you want to be "plugged" in all the time and what not in each application- handheld and more stationary.
Isn't that what Microsoft is doing with Windows 8?
So Apple is going to combine iOS and OSX in four years or less and make a single operating system that works across all of Apple devices. Microsoft is making Windows 8, this year, which will run on multiple hardware.
That''s great, but I worry they will have one operating system that works best for one of their devices instead of two operating systems that make the most of the two different streams of devices... or is that just me?
Ron W
If Apple is able to give one OS across iPhone, iPad and the Macs, and make it work well at different levels on each device depending on the device capability, that would be fantastic. That would change the game of computing forever. But it has to work well on all the devices. That is going to be tough. 
I think Microsoft already does this. The current Windows Platform runs on the desktop and the phone.

It's not the greatest in the world due to the limitations that the phone platform places on applications, but it is viable.

So go ahead Apple and make the same mistake.

When will engineers learn that you can only take a platform so far before you have to step back and see the reality that it's not the OS that makes this work but the development tools. Until you come up with a dev platform that truly takes your code and let's it run on any platform this going to fail.

It's just like telling iPhone developers, " Sure you can write apps for both the iPhone and iPad with one set of code, however you'll need to include two different screen types, one for the iPhone and one for the iPad."

Now to add your app to the desktop, you'll only need to include yet another set of screen for that platform. Not a big improvement in my book. I think a lot of devs are already doing this. So, I don't see any benefit in this. Kind of reminds me of Apple's multi-language platform. Not very efficient at all. I'll wait until the third party library comes out to take one screen definition and translate it to every platform for me, otherwise I'm wasting my time. 
That would be awesome!
+Jim Lavin I can't imagine wanting to build the same views for various screen "types". Generally you want to rake advantage of the display format you're working with. If your developing using good patterns correctly (MVC,MVVM, etc) the code for the "screen" (or View) is very minimal - all the heavy lifting is in the controllers and model. The problem your talking about is already being tackled on multiple platforms including iOS, OSX, Java/Android and .Net/Windows/Phone. 
+Jason Ehle You are 100% correct about using patterns, without them my job would be very repetitive and boring.
Both iOS and MacOS X are Unix underneath. Given how many OS are based on Unix, Unix is the OS that rules all.
Add a comment...