> I also still don't have a comfortable dev experience on the M1
Interesting. What is that you dev?
I'm not an apple developer at all, but my dev experience with both Java and Go has been pretty frictionless.
My Air is my secondary machine, but that's only really because my workstation is a 16 core/64GB AMD machine and does our product build and test run in about half the time the Air does, which itself is half or less the time previous laptops did. But in the few months that this machine was in transit, the Air did a great job.
> I'm not an apple developer at all, but my dev experience with both Java and Go has been pretty frictionless.
Same. Java, Go, and web dev is my every day. Not an exactly fair comparison, but my first M1 MBA replaced a 2017 MBP, and it cut my java test suit times in half. 16GB wasn't quite enough RAM for all I do so now I'm a 64gb MBP M1.
I've thought about building a Ryzen desktop and just running linux, but I don't want to split between two machines and need to be mobile.
I'll chime in here. I have the same experience (Julia, R, JS, and a little bit of C/Python). I have an M1 laptop that I use constantly, but I'm lucky enough to have the opportunity to remote into my working environment.
If I had to use my M1 laptop has my main development machine, I would think very hard about trying to pick up a T14 or something similar.
Library compatibility issues, in particular with Julia and R.
It's gotten much better over the last year, but I still run into enough problems that I try to keep all of my actual development work on a remote machine.
A few years ago I was using R on OpenBSD. OpenBSD somewhat aggressively removes deprecated features as compared to Linux and macOS. It was really eye-opening to see how bit-rotted some parts of the scientific / numeric ecosystem are. I ended up submitting some trivial PRs deep in the stack for use of system calls that have been deprecated but not removed from Linux for a decade or more.
Interesting. What is that you dev?
I'm not an apple developer at all, but my dev experience with both Java and Go has been pretty frictionless.
My Air is my secondary machine, but that's only really because my workstation is a 16 core/64GB AMD machine and does our product build and test run in about half the time the Air does, which itself is half or less the time previous laptops did. But in the few months that this machine was in transit, the Air did a great job.