The biggest hurdle for me was JavaFX, the UI libraries we use to teach students the Model-View-Controller principle. Gradle 6.7 builds fine with the ARM64 development kit. I settled for v15, since Gradle does not like Java 16 yet, according to the compatibility matrix. They even ported the JDK13/JDK11/JDK8 older ones. There are other solutions, but the Zulu builds I tested so far are great. The Azul community released ARM64 Java builds that are blazingly fast. The Gold is a bit more Pink than I'd like, but it's growing on me! Java development For now, “it just works”, but as Evernote, is far from optimized. I’d like to run as much stuff as possible native, I guess we’ll have to wait. Spotify is a mess, according to some, while others claim that Rosetta is “good enough”.
bash_profile file in my home dir to set the path for Sublime Text 3 builds. Fiddling with the internal exec.py file did not work for me. There are a couple of options to mitigate this. This means that your $PATH will be screwed up. 2021: Sublime Build Systems still use /bin/bash to execute the exec_cmd or cmd commands. 2021: The latest GIMP 2.10 is finally released for OSX, but there are known Big Sur issues. The Rosetta one works, but is a bit sluggish and uses a significant amount of battery. It runs on Electron, a known-to-be CPU hungry JS shell.
MACOS CLIPY CODE
Preview builds of Visual Studio code are already released. Clipy clipboard utility, the upgraded ClipMenu one.Still on Rosetta - but development on the way: Alfred - of course! I became a convert after fiddling with it, replacing Spotlight and Clipy (see below).(Heads up: unrar is gone! See link for alternate formula.) I set up the M1 homebrew version in /opt/homebrew - and so far, every installation didn’t need a Rosetta alternative - yet. I’ve successfully built these from source: sqlite, openssh, python3.9, imagemagick.
MACOS CLIPY INSTALL
The master branch of Homebrew is ARM64-complaint and you can install two homebrews for the bottles that are still lagging behind - or compile them from source using brew install -build-from-source. Now that you have a shell, we need cmdline stuff. Check out ’s oh-my-zsh config for colors and such, and maybe add extras in your ~.zsh. It’s already M1-ready, and Big Sur moved from Bash to Zsh, another good shell I still know from my Gentoo days. I don’t care about CPU throttling - even with the 25% performance hit, it still outperforms heavyweight Intel MacBook Pros! Productivity toolsīefore getting to the programming part, let’s take a look at the basic tools I couldn’t live without. I went with the 512GB Air version with eight cores.
MACOS CLIPY UPGRADE
Whatever you do, be sure to upgrade Big Sur to 11.1 first - that will take a while (and eat up more HDD space).
MACOS CLIPY SOFTWARE
An interesting site to check whether your software works is and - although these are not always up to date and sometimes provides false information! Be sure to go after the source yourself. Bear in mind that this will very likely change in the near future, as many developers are starting to support the new architecture. But hey, what the heck.Īs there’s not a lot of information out there on the M1 from a developers perspective, except a few other blogs here and there, I wanted to chime in and share my initial findings.
At first, I wanted to hold off for a while, after many of the developer tools I use were officially supporting ARM64. So, Santa (well, you know) bought me a M1 2020 MacBook Air. My 2012 MacBook Air was in need of a replacement, and although still very serviceable for a 8+year old laptop, not upgrading OSX and a shortened battery lifespan were getting irritating. Fuckery article, I couldn’t stop wanting one. Ever since I read Kay Singh’s Apple Silicon M1: Black.
0 kommentar(er)
