Do we open Terminal and go to `brew install` a bunch of development tools... and then it hits us... this machine is cool and all, but half the stuff we need to get work done does not build or run on arm64?
Do we open Terminal and go to `brew install` a bunch of development tools... and then it hits us... this machine is cool and all, but half the stuff we need to get work done does not build or run on arm64?
It would be a big job, but much of the software on Homebrew is already ARM compatible, and I think there’s a clear path to supporting that, which should make the migration relatively seamless for most developers I’d imagine.
It won’t be without issue, but I don’t think it will hurt macOS as a development OS much in the long run.
Maybe Adobe will finally take Linux seriously if that happens.
I may have also spoken imprecisely. Ultimately what I mean is this: I can copy a binary or a package compiled for Ubuntu, Debian, RHEL, what-have-you, targeting the Linux kernel, and I can run or install that in Windows Subsystem for Linux as is.
Here is the sources.list from Ubuntu 18.04 on Windows, with comments removed:
deb http://archive.ubuntu.com/ubuntu/ bionic main restricted
deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted
deb http://archive.ubuntu.com/ubuntu/ bionic universe
deb http://archive.ubuntu.com/ubuntu/ bionic-updates universe
deb http://archive.ubuntu.com/ubuntu/ bionic multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-updates multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu/ bionic-security main restricted
deb http://security.ubuntu.com/ubuntu/ bionic-security universe
deb http://security.ubuntu.com/ubuntu/ bionic-security multiverse
No special sauce. Just Ubuntu packages.