Sharing a lot of components isn't the same as being 'the same'. Time to pick up the dictionary.
Can you prove that the code of iOS is exactly the same as the code of OS X? Because it clearly is not, which makes them different.
Besides, what does the code have to do with anything? Even a child can see that OS X and iOS aren't the one and the same.
The discussion was about "merging" them. This is a tad bit more than just a superficial "Joe average" "they're different!". Look, if you don't want to discuss the actual "merging" of things that are already pretty much merged on a component basis, fine, just let it be though, don't go running around with you're "they're different!".
And clearly OS X and iOS are not using the same code ? Sorry, I think you need to go look at how both OSes are made. There is a lot of code sharing there.
Your original claim was that iOS and OS X are different because OS X runs x86 binaries and iOS runs ARM binaries, something completely unrelated. You can have different OSes run the same binaries (FreeBSD on x86 can run Linux built and targetted binaries) and you can have the same OS on different architectures incapable of running the same binaries (Linux x86 vs Linux ARM). My original point was 2 folds :
- Discussing a merging of OS X and iOS as if it was the end of the world is dumbfoundingly stupid. The plain fact is Apple will always reuse code between both but they can never be completely identical because of the device form factors they run on requiring different UI paradigms.
- Trying to tie any such difference between these 2 OSes to CPU architecture is as dumbfoundingly stupid. OS X could very much run on ARM as is and iOS could run on x86 as-is also. ARM based desktop processors could be quite viable, and medfield SoCs are x86 processors and could run in the next iPhone for all we know.