Im curious to know what software are you afraid to lose?
A lot of people are concerned about losing Intel software support on Mac after the Arm transition.
They didn't talk about this during the announcement, but I am worried that transition to Arm will lead to the MacOS becoming more locked down like the iOS.
More specifically, the ability to use software that didn't come form the App Store. Most of the software I use did not come from the Mac App Store.
I am unsure if that will happen, or maybe happen down the road, but hopefully never.
The other concern I have is with software that is no longer updated by the developer.
Maybe with Rosetta II this won't be a big deal, but Apple dropped support for the original Rosetta relatively quickly, so this might happen with Rosetta II also.
They demoed Photoshop, which isn't available on the App Store.More specifically, the ability to use software that didn't come form the App Store. Most of the software I use did not come from the Mac App Store.
That worries me too, but they made the point of showing Parallels and if they dropped Virtualization support that would immediately kill such an app unless Parallels wrote their own emulator. Virtualization is a big deal for developers - I use it all of the time for testing software on old OS versions, so I can't see them killing something like that at least for several years. Kind of like how we got over a years warning before 32-bit apps got dropped.Maybe with Rosetta II this won't be a big deal, but Apple dropped support for the original Rosetta relatively quickly, so this might happen with Rosetta II also.
I will miss Fusion because without it I can't use a Mac at work and Rosetta is not going to work on it.
How are they going to allows cross-platform applications using X11 for the GUI to run on macOS, many of which are not specifically designed for macOS. This includes numerous scientific and academic software projects.
Will I be able to run command line tools from terminal (a python script for example)? Is python or Rstudio going to work at all?
Is it possible to connect to a server via Terminal and launch a non-Mac applications with its GUI?
What happens to the Unix based language?
None of that will change in macOS 11. They haven't removed the Terminal and macOS is still a unix based operating system. Python and X11 are open source, so something like homebrew (once updated to support the new OS) can still be used to install it.Will I be able to run command line tools from terminal (a python script for example)? Is python or Rstudio going to work at all?
Is it possible to connect to a server via Terminal and launch a non-Mac applications with its GUI?
What happens to the Unix based language?
Motorola chips weren’t proprietary. They were just different. 68K and PowerPC chips are still in use in embedded applications (cars, ATMs, etc).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?
It 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.They demoed Photoshop, which isn't available on the App Store.
That worries me too, but they made the point of showing Parallels and if they dropped Virtualization support that would immediately kill such an app unless Parallels wrote their own emulator. Virtualization is a big deal for developers - I use it all of the time for testing software on old OS versions, so I can't see them killing something like that at least for several years. Kind of like how we got over a years warning before 32-bit apps got dropped.
Edit: The platform state of the union confirmed they were showing ARM Linux, not emulated x86 Linux. And they worked with Parallels to make that possible. They also confirmed (which should be obvious) that they're shipping full copies of the x86 binaries to make Rosetta possible. Which means they will want to get rid of in the future to save space. It's likely they will probably do the same thing as last time, where it's included by default initially, then optional in a later OS before they eventually remove it. I hope VMWare or Parallels comes up with a solution for x86 support and it performs decently. I know Codeweavers has Crossover (WINE) for Android that does x86->ARM translation, so I hope they port that to Mac too. But I feel bad for them after the hassle they went through last year writing their x86->x64 translation.
This is where I am with this transition as well.I will miss Fusion because without it I can't use a Mac at work and Rosetta is not going to work on it.
None of that will change in macOS 11. They haven't removed the Terminal and macOS is still a unix based operating system. Python and X11 are open source, so something like homebrew (once updated to support the new OS) can still be used to install it.
The only thing this really changes for open source stuff is likely a need to recompile for ARM. If you already used a package manager like brew you were already compiling stuff yourself.
let’s see if Homebrew will get any support on ARM at all... isn’t it cheaper and easier for people to simply switch to Windows/Linux/Ubuntu?
Also, I don’t know if it’s easy to recompile to ARM from compiled application for x86. To what extend are people willing to work on this?
I will miss Fusion because without it I can't use a Mac at work and Rosetta is not going to work on it.
There is absolutely zero reason to be concerned about the Unix and homebrew ecosystem on an ARM macOS machine. 99.999% of the software in homebrew is already ported to ARM and the only real difficulty will be for the homebrew architecture to be able to handle multiple architectures.
All the applications and tools you mention have been running on ARM Linux for about a decade now. Getting them working on ARM macOS will be trivial.
This is correct.There is absolutely zero reason to be concerned about the Unix and homebrew ecosystem on an ARM macOS machine. 99.999% of the software in homebrew is already ported to ARM and the only real difficulty will be for the homebrew architecture to be able to handle multiple architectures.
All the applications and tools you mention have been running on ARM Linux for about a decade now. Getting them working on ARM macOS will be trivial.
Active Trader Pro (ATP) from Fidelity Investments, their real-time trading tool. This is a Windows executable and up until about six months ago was still 32-bit.
It runs on macOS, packaged in a customized version of CrossOver. Fidelity retail investors were warned at Catalina's release that ATP was not compatible (at the time) and that Mac users should stay on Mojave. Eventually ATP was updated as a 64-bit Windows application and the Mac version followed a while later.
The Mac version of ATP (running in CrossOver) performs decidedly poorly compared to the same executable running natively on a Windows box regardless of whether it's Mojave or Catalina.
ATP is so well optimized for Windows, I prefer running it at home on a $170 cheapo Wintel PC rather than my Mac mini 2018 that was >10x more expensive. Likewise, I prefer running ATP on a $745 Acer notebook PC rather than my $1650 MacBook Air 2019 when I'm on the road.
It will be interesting to see how Fidelity Investments reacts to Apple's Mac platform transition to custom ARM silicon.
Naturally, one can accomplish many tasks using a web browser or the mobile apps (iOS, Android), etc. but the latter two aren't the same as the full-blown desktop tool.
Active Trader Pro is probably the most glaringly obvious piece of Wintel software that I would miss at this time.
This is correct.
All of the Linux crappiness that I endured in the late Nineties on Wintel hardware I can still experience on ARM hardware.
Back then I ran Red Hat Linux 5.2 and 6.0 or Gentoo Linux on Intel hardware (Pentium II, Pentium III, Asus motherboards, Matrox Millenium graphics cards, etc.).
Today it's Raspbian and LibreELEC on an ARM-powered Raspberry Pi 3.
And desktop Linux still sucks rocks. Poor device drivers (especially notebook PC power management), piss poor end user documentation, and excessive system administration load. Dependency hell is still a real issue. And the desktop environment UI looks like it was designed by a 10 year old.
F***ing Raspbian can't update itself even with a live WiFi network connection; I still need to plug in Ethernet. At least with LibreELEC I can avoid most of that dependency hell by downloading a complete image image with wget then rebooting to complete the upgrade.
So yeah, all of the major *nix applications are all available on ARM.
Desktop Linux on ARM sucks just as bad as Linux on x86/i64. The same experience is pretty much guaranteed.
Trust me, I still think Linux is a great operating system for servers, ATMs and smart doorbells, etc.