Agreed. Apple Mac Device is a lot more expensive and does not have the large quantity of market share and user base to accelerate ARM architecture adoption.
You have it backwards. The purpose of ARM is to accelerate Mac adoption and market share.
Agreed. Apple Mac Device is a lot more expensive and does not have the large quantity of market share and user base to accelerate ARM architecture adoption.
You should go tell VMware, Parallels, the VirtualBox team at Oracle, the XEN team, not to mention Intel and AMD that hardware assisted virtualisation is not a big deal, and we can all go back to pure software VMs from the 90s, shall we?
Apple has already removed most of the legacy problem by removing support forCocoaCarbon, and for 32-bit apps (as they did in the past by removing support for 24-bit 68k and for PowerPC).
I agree that this problem is overstated by some - but it can be understated as well.
Apple added 64 bit app support in OS X Leopard in 2007 - so there will be 64-bit apps out there that are 10+ years old. Even where "porting" then would be as simple as checking the ARM box on XCode and hitting "build" that assumes that the developer is still in business and willing to support 10 year-old apps.
Of course, if you have the source code that's potentially different.
...and, ultimately, only the developers involved can tell you if there are any x86 dependencies in (say) MS Office or Pro Tools, or the myriad of Logic Pro plug-ins and - if there are - how much re-writing would be needed. (However, if there's too many, that does sound like carelessness, and getting software using standard frameworks is a Good Thing anyway...)
I don't think the instruction set itself is protected, but some implementation patents at least in amd64 likely still are. I'm not sure they apply to an emulation or translation layer though. For sure examples of such solutions already exist:
- Windows on ARM has an x86 to ARM translation layer which allows x86 applications to run on ARM without the need of being recompiled.
- QEMU supports emulation for a lot of different architectures, including x86-32 and amd64.
Apple should be able to support two architectures and perhaps that's what they will do. With catalyst and the ability to compile binaries to specific architectures it would make sense. While Apple's ARM design seems great on low power and portable devices I wonder how it would perform scaled up vs. high end offerings from AMD and Intel x86/64.
It might not be true for everyone, but they will loose a lot of short and some long term business if they jump to ARM and dump x86 completely. They would probably emulate code like they did with Rosetta and PPC, though I doubt performance would be comparable to native architecture unless they optimized like crazy.
One of the main reasons I like mac hardware is the ability to virtualize and run bootcamp allowing tons of flexibility and use. I suppose it depends if the PC industry as a whole transitions to ARM, though I only see that for low powered devices.
If Apple releases an ARM Macbook / Air with passible x86 emulation, but keeps the x86/64 line for the "Pro" series that seems like a smart move.
If you need to run old apps then currently you already screwed by Catalina. x86 VM will not help you at all.
You have no clue what I use a computer for, but somehow you think that an architecture translation layer inside a virtual machine is "good enough". Whatever you're smoking, I'd cut back.If you just need Windows x86 app then running a ARM windows VM and using Microsoft's x86 compatibility layer is good enough for you.
If they did, history says it will be supported for a very short time - which doesn't solve the issue for anyone who needs/wants to run x86 software on an ongoing basis.And do you really thinking Apple will not build a Rosetta 2.0 for this transitioning?
You have it backwards. The purpose of ARM is to accelerate Mac adoption and market share.
.... What "advertising"?You're believing their advertising.
I literally use it every day for my job. I'm not sure how using a technology feature is a 'weird obsession'?You have a weird obsession with virtualization
I wasn't particularly aware of the ARM hardware support no - but that's kind of pointless, because as I said: running an ARM virtual machine with hardware acceleration doesn't really help at all, if what you want to do is run an x86 VM, does it?not realizing that ARM already implemented this
Hence the relevant market to look at is desktops and laptops, where ARM is undeniably the minority architecture.
You have literally no clue what you're talking about. I literally run a macOS Sierra VM on Catalina, with 32bit apps in it.
You have no clue what I use a computer for, but somehow you think that an architecture translation layer inside a virtual machine is "good enough". Whatever you're smoking, I'd cut back.
If they did, history says it will be supported for a very short time - which doesn't solve the issue for anyone who needs/wants to run x86 software on an ongoing basis.
That's *apple's* main purpose. To sell more machines, because the machines will be better, they can make them in more form factors, and they will be more compatible with iOS.That's not the main purpose of using ARM architecture.
Hell, there are typically ARM processors in the power bricks on these things.Actually, most laptops and desktops likely already have more ARM processors in them than x86.
12” MacBook making a return?
That's not a very short time. And during snow leopard I hardly use any PPC app anymore.
Fascinating. Provided this is true, and happens on time, and we get a 10.16 later this fall as in line with past years, then 10.16 will be the first macOS version since 10.4 to go through a processor transition.
LOL. If every single person who even remembered that powerbooks were a thing were to buy the new machine, it would still be small potatoes for apple.I think this is an excellent move on Apple's part. Going to Intel was a necessary evil back in 2005 and was a good decision at the time. If they want to really nail this launch, they need to bring back the Powerbook name. That marketing aspect alone would secure the transition back to an Apple-controlled architecture.
.... What "advertising"?
Oh, this answer wasn’t about “openness”. The OP was being told that Intel does things no other processor can do, and my answer was that any processor can do anything as long as you provide it the right instructions. The OP’s question was just at the CPU level, not what happens when a vendor tries to lock it down (and, with jailbreaking, even locking down doesn’t stay locked down forever).The reason you have so much open source support for Raspberry Pi is because of its open design.
With locked down hardware and OS there will be no open source community.
I use one macOS VM, to run one macOS only App, specifically because the newer versions of this app don't support the self-hosted mode they supported formerly, because said app developer said "**** you" to those of us who bought a license to run it self-hosted.You already using a VM to run your apps. If the app developer still supporting the app they will definitely want get out of that situation as software need customer to get them money.
And you do not have to throw away your current computer. You can keep it during the transitioning time just like how everyone keep using their G4 in 2007.
Intel can sue at any moment, they just choose to stay put so far.
You mean, the one released a decade and a half ago? And iteratively improved since then?the original VT-x
Totally agree with you. Bootcamp is part of Apple computers since 2005 (or so). Cannot be thrown in garbage. Its essential for many users out there.I need Bootcamp. Period. I *don't* want a slow virtual layer between me and the Windows apps I need to run.
The reason you have so much open source support for Raspberry Pi is because of its open design.
With locked down hardware and OS there will be no open source community.
Totally agree with you. Bootcamp is part of Apple computers since 2005 (or so). Cannot be thrown in garbage. Its essential for many users out there.