Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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?

You're believing their advertising. If you actually ran the numbers, it took them about two generations for hardware assisted virtualization to get a performance boost. Even today, you need features like SLAT to gain over software, which by the way, is supported since ARMv7.

You have a weird obsession with virtualization, not realizing that ARM already implemented this in every smartphone today for security and DRM purposes. And again, one of the iPhones, in the 4 era I believe, ran under a hypervisor to fix a security issue.
 
Apple has already removed most of the legacy problem by removing support for Cocoa Carbon, 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 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...)

To be fair, if you are running a 10-year-old app, it's just as likely that it will stop working in 2020's MacOS Port of Oakland for reasons other than ARM. Apple has been on a tear shedding old SDKs, requiring new entitlements, etc., and backward compatibility has never been a huge Mac OS hallmark.
 
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.

Intel can sue at any moment, they just choose to stay put so far.

See cases here




 
  • Like
Reactions: cmaier
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.

Exactly, it will be ridiculous to completely dump x86 for the Pro Series.
 
If you need to run old apps then currently you already screwed by Catalina. x86 VM will not help you at all.

You have literally no clue what you're talking about. I literally run a macOS Sierra VM on Catalina, with 32bit apps in it.

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.
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.

And do you really thinking Apple will not build a Rosetta 2.0 for this transitioning?
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.
 
You're believing their advertising.
.... What "advertising"?

You have a weird obsession with virtualization
I literally use it every day for my job. I'm not sure how using a technology feature is a 'weird obsession'?

not realizing that ARM already implemented this
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?
 
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.

Rosetta started with Mac OS X Tiger 10.4
And was removed in Mac OS X Lion 10.7.

That's not a very short time. And during snow leopard I hardly use any PPC app anymore.

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. Catalina is already pushing them to move forward. 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.
 
That's not the main purpose of using ARM architecture.
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.
[automerge]1582651968[/automerge]
Actually, most laptops and desktops likely already have more ARM processors in them than x86.
Hell, there are typically ARM processors in the power bricks on these things.
 
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.
 
That's not a very short time. And during snow leopard I hardly use any PPC app anymore.

Again, you're missing the point - I have to assume deliberately.

At the time of Apple's transition to Intel, there was essentially no commonly used software that ran on PPC other than that which targeted Mac OS.

In the ~3 versions/5 years of macOS supporting Rosetta, it was reasonable to expect Mac app developers to rebuild their apps for Intel - there was certainly no expectation of new, ongoing development of PPC-only apps that would not be available for Intel at all.

In this scenario, that is not the case at all. Unless you're expecting the majority of the computing industry to drop x86 by the time Apple decides to drop a hypothetical "Rosetta 2.0"?
 
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.
 
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.
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.
 
.... What "advertising"?

Intel and the hypervisor companies. Test showed that the original VT-x led to more overhead and lower performance than software-based virtualization, simply put it made it worse. It was found that it is not sufficient to merely trap privileged instructions, but you have to include the whole IO (VT-d) and memory (SLAT) architecture in it.

It's a perfect example x86's legacy tax. ARM was built with exception levels and people use it, thus they form a good base for virtualization. x86 has privilege rings, but for legacy reasons, DOS and Windows ignored most of it and AMD64 deleted what remained, so when virtualization became a thing they had to go back in and hack in more levels.
 
Last edited:
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.
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).
 
  • Like
Reactions: cmaier
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.
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.
My point about that wasn't that it's a huge use-case, it was that you have literally no ****ing idea what you're talking about claiming that an x86 VM can't help alleviate the 32bit issue for "legacy" Mac apps.

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.

Somehow, you've still missed the point completely. 99% of my use for x86 VMs is not "legacy" software. I use a metric **** ton of VMs to run simulations of production x86 Linux environments, locally. This is not a rare thing for developers using Macs, and while some would get by with an ARM Linux VM, plenty wouldn't be able to.

"just keep using your old computer" isn't really a viable solution if Apple drops all x86 support.
 
Intel can sue at any moment, they just choose to stay put so far.

It's true. I just drove through Santa Clara and saw a bunch of Intel lawyers hiding in a tree, waiting to pounce on any emulator makers who have the misfortune to pass under them on route 101 this morning.
 
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.

Apple has millions of paying registered developers. As well as those developers being a huge fraction of their market share in laptops, it's also the big reason for their multi-billion dollar success in iOS devices and services. And developers need to install their code (or open source code) to debug it and test it.

So Apple can't lock down macOS.
[automerge]1582654322[/automerge]
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.

Many does not equal a highly profitable fraction of Apple's laptop sales. Maybe a few percent, which they can make up for in revenue by pushing a few more in-app-purchase things.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.