If I install Big Sur on my Intel iMac, does that mean everything that runs on it goes thru a translation layer? Or is there 2 separate codebases and 1 gets installed depending on what processor you have? What the hell is going on under the hood?
Ah.. thank you! I tried to reason whether it was native either way and neither made good sense. This would explain a lot!Big Sur contains both the arm64 and the x86_64 parts. See https://en.wikipedia.org/wiki/Universal_binary
There is ONE codebase for Big Sur. This is translated to 64 bit Intel code and 64 bit ARM code. The technology for this has been available since 2005 I believe.If I install Big Sur on my Intel iMac, does that mean everything that runs on it goes thru a translation layer? Or is there 2 separate codebases and 1 gets installed depending on what processor you have? What the hell is going on under the hood?
So that means you could put Big Sur on an external SSD and use it on both an Intel Mac and an M1 Mac? That's pretty cool.There is ONE codebase for Big Sur. This is translated to 64 bit Intel code and 64 bit ARM code. The technology for this has been available since 2005 I believe.
Yeah, I heard of Universal binary before, but thought it was just for apps and it never occurred to me that the same concept could be done at the OS levelThere is ONE codebase for Big Sur. This is translated to 64 bit Intel code and 64 bit ARM code. The technology for this has been available since 2005 I believe.
I thought I read somewhere that this doesn't work? Needs more testing.So that means you could put Big Sur on an external SSD and use it on both an Intel Mac and an M1 Mac? That's pretty cool.