Performance-per-watt. The principle metric when designing chips.Can anyone work out the logic here?
Apple used to use Motorola to make proprietary chips, then to Intel and now back to another proprietary chip, this time with Arm?
Performance-per-watt. The principle metric when designing chips.Can anyone work out the logic here?
Apple used to use Motorola to make proprietary chips, then to Intel and now back to another proprietary chip, this time with Arm?
Johny Srouji clearly pointed this out in the first minute of his appearance in today's WWDC keynote.Performance-per-watt. The principle metric when designing chips.
Apple has never prioritized compatibility when switching CPU architectures. This transition might be the closest to doing so yet since all of Apple’s platforms now run on the same architecture.Today, Apple unveiled that decision. They are prioritizing factors other than compatibility for their next-generation computing architecture.
For now it isn't, but this could very easily change, especially if Apple starts restricting MacOS apps to only ones in the App Store.They demoed Photoshop, which isn't available on the App Store.
But for the Intel software do you have software you use that you are afraid will be left behind?
Yeah, it is hard to say specifics without knowing which ones won't be supported. I also had SheepShaver in mind. I also wonder about Handbrake and MakeMKV. There are a few others that I have that are no longer supported by the developers (or hasn't been updated in years), too.t's hard to say which software I will miss - because likely I won't be aware of the incompatibility before its too late.
This is also my thinking.It's the small/indie devs with limited budgets and time that will be lost in the translation.
Apple used to use Motorola to make proprietary chips, then to Intel and now back to another proprietary chip, this time with Arm?
Can anyone work out the logic here?
Apple used to use Motorola to make proprietary chips, then to Intel and now back to another proprietary chip, this time with Arm?
In one of the videos, the presenter was talking about how Intel apps will be translated for Arm upon installation, when installed from the App Store or from a .pkg. He continued to say that if you install some other way then it'll be translated upon first launch.For now it isn't, but this could very easily change, especially if Apple starts restricting MacOS apps to only ones in the App Store.
MacTheRipper
I wonder how long it will take for Handbrake to go Arm.
It's not that I'm concerned there will never be compatible versions, just that it might take a couple years.
Vectorworks
Lightwright
AutoCad
EOS Family Software
Augment 3D
QLAB
Cinema 4D
Quicken gave up on Mac parity a long time ago. I moved to Banktivity and find that works better than any Mac Quicken version I ever triedIt seems obvious to me (not a developer) that Apple moved everyone to x64 because they didn’t want to translate all the legacy x86 instruction set with crud all the way back from the early 1980s. They wanted to focus on x64.
Since Codeweavers already wrote the 32-to-64 bit translator, hopefully the port to Rosetta 2 still works for a few more years. Maybe then Quicken can write a Mac app with feature parity and I can stop using Windows apps entirely.
Motorola chips weren't proprietary. The 680x0 was used by a great many machines-- Macintosh, Amiga, Atari ST, pre Sparc suns, Sharp X68000. The PowerPCs were used by IBM and Be (plus a whole load of MacOS clones...). The ARM chips are probably the most proprietary of these CPUs.Can anyone work out the logic here?
Apple used to use Motorola to make proprietary chips, then to Intel and now back to another proprietary chip, this time with Arm?
I'm still on Mojave, but all my regularly used apps, including all my dev tools/services are all 64-bit, and while I realize several of those won't be ARM in the short term, I suspect eventually __and__ they're pretty lightweight apps (for example, Postman), so that they;ll be good for running under Rosetta.
I have time to figure out my few Winders™ needs, some things I've moved to Docker, some to cloud services, I'm definitely in a wait-and-see mode on a few things, but I can say, I'm mostly excited
I'm hoping this means an A13X/Z or A14X/Z powered Mini with a kickass GPU in the next 8-12 months
Postman is mostly JavaScript in a special build of Chrome. Once Chromium has an Apple Silicon build, it shouldn't take long for Postman to adopt it.
The WWDC porting session today confirms that Rosetta 2 cannot be used for Virtualization.
With yesterday’s Parallels demo confirmed to be running ARM Linux instead of x86 Linux during the state of the union video, it looks like any software for running Windows on ARM Macs will need their own emulation. Rosetta has an advantage with macOS apps because they can be translated ahead of time if they're not JIT and have very little performance impact as a result, but such an advantage won't exist for running an entire operating system in a VM. It will be interesting to see what kind of performance parallels ends up with for Intel emulation, which I assume they're going to do considering running Windows is the main selling point of their product.
For those worried about loosing Windows support, there is still another shoe to drop. Microsoft has developed an Arm version of Windows 10. It's not completely done yet but the roadmap to completion is not that long. Let's see what they do. In the meantime, It looks like Parallels is working with Apple. Let's see what that brings. VM Ware is not a stupid company, they might have something up their sleeve yet to come.
That's the only option. It's not virtualization if the code is not native. You're just creating a virtual space inside your existing environment for the original code to run, nothing needs to be translated.Any idea on how people will virtualise Windows? Only with Windows 10 ARM version I suppose?