So, my trusty M1 Macbook Air running Asahi Linux is, well, trusty, but it doesn’t have the screen space and power I really want out of a personal workstation. So, I took a look at what Macs Asahi Linux supported, saw that M4 support isn’t coming anytime soon, and did the open source right thing and bought an older one decided to give macOS another try.
My Reasoning Beforehand There were a few reasons I ended up deciding to do this.

The Coded Message's resource offers insights, tutorials, and resources for software developers and technology enthusiasts. Readers can learn about coding best practices, software architecture patterns, and emerging technologies. With articles, tutorials, and code samples, The Coded Message provides  guidance and expertise for building software applications and advancing technical skills.

The Coded Message

A developer shares their experience switching from Asahi Linux to macOS for daily work, evaluating window management, CLI tools, VSCode integration, and the Unix layer. They discuss practical workflow changes (adopting VSCode, preferring full-screen apps), technical quirks (permission dialogs for CLI tools, Finder limitations), and philosophical tensions between convenience and open-source customizability. The review concludes that macOS works well for their current needs despite reservations about vendor lock-in and reduced system control.

Review of macOS for Serious Work

<p>So many of these issues are resolvable by just googling.
The user complains that the OS is not customisable, without looking at how to customise it.
Literally:
“First off, that thing I pointed out, where I can’t switch between windows with a key combo, only between apps—that’s annoying. And it’s more philosophically annoying because I’m at the mercy of Apple about it, which is unnecessary.”
Just google it? There’s a shortcut for cycling apps, and a shortcut for cycling windows of an app.
Am I supposed to believe this is an ex-linux user?</p>
