A year of Nix on macOS

2026-01-17T00:00:00+00:00
I remember the exact moment I decided to try Nix. It was a Thursday night, somewhere around 11pm, and I was staring at a broken terminal after a macOS update had silently reset my dock preferences, broken three Homebrew symlinks, and somehow changed my default Python. Again. I'd been maintaining my dotfiles since January 2021 (vim plugins, zsh themes, git configs, the whole ritual) and every few months something would just... stop working. No clear reason. Just vibes.</p>
So on January 17, 2025, I added a flake.nix</code> to my dotfiles repo. I had no idea what I was doing.</p>
The before times</a></h2>
Let me paint the picture of what I had. A .zshrc</code> that had grown organically over four years. A Brewfile that was mostly accurate. An install.sh</code> that I wrote once, ran once, and never touched again because I was afraid of what it would do. Config files scattered across ~/.config/</code> with no clear record of which ones I'd manually edited and which ones came from the repo.</p>
The setup worked</em>. I could write code, push commits, deploy services. But every time I needed to set up a new machine or debug a broken path, I'd spend half a day reading my own shell history to figure out what I'd done six months ago.</p>
The worst part was the terminal emulator situation. I'd gone from Alacritty to Kitty to Ghostty, and each migration left behind config files, PATH entries, and font caches that I'd forget about until they caused some weird conflict.</p>
Finding Nix</a></h2>
Nix is one of those tools that everyone describes differently. "It's a package manager." "It's a build system." "It's a functional programming language for system configuration." All of these are technically true and none of them helped me understand why I should care.</p>
What finally clicked was this: Nix lets you describe what your system should look like, and then it makes it look like that. Change the description, it computes the diff. Break something, roll back. Nothing else to it.</p>
On macOS, nix-darwin</a> extends this to system-level stuff (Homebrew packages, macOS defaults, keyboard mappings, firewall rules) and Home Manager</a> handles the user-level things (dotfiles, shell aliases, environment variables).</p>
My system is now two files and a Makefile. flake.nix</code> for the system. home.nix</code> for my user environment. make rebuild</code> to apply everything. No install script. No manual steps. No "did I remember to run that command."</p>
How it actually happened</a></h2>
It wasn't instant. Looking back through my git history, I can trace exactly how it unfolded.</p>
The first flake.nix</code> in January 2025 was cautious. I just moved a few packages in: neovim</code>, ripgrep</code>, jq</code>, rustup</code>. I also added nil</code> (the Nix language server) and nixfmt</code> because editing Nix files without tooling is like writing Rust without rust-analyzer. Technically possible, practically miserable.</p>
Two months later I added Home Manager, and that was the moment everything changed. Before, I was symlinking config files with a shell script and crossing my fingers. Now I could just declare them:</p>
home</span>.</span>file</span>.</span>"</span>.config/ghostty/config</span>"</span>.</span>source</span> =</span> ./config/ghostty/config</span>;</span></span>
home</span>.</span>file</span>.</span>"</span>.config/git/config</span>"</span>.</span>source</span> =</span> ./config/git/config</span>;</span></span>
home</span>.</span>file</span>.</span>"</span>.config/zed/settings.json</span>"</span>.</span>source</span> =</span> ./config/zed/settings.json</span>;</span></span></code></pre>
Change the source file, run make rebuild</code>, the symlink updates. No ln -sf</code>. No checking if the target exists. No cleanup of stale links from three terminal emulators ago.</p>
Then in May I made a mistake. I tried to manage Homebrew entirely through Nix using a thing called nix-homebrew</code>. The idea was beautiful: one system to rule them all. The reality was fragile. Homebrew really wants to own its own state. Taps, cask tokens, update cycles. It has opinions about these things, and fighting those opinions was causing more problems than it solved.</p>
So I ripped it out. Instead, I let nix-darwin manage Homebrew declaratively</em> without trying to replace</em> it:</p>
homebrew</span> =</span> {</span></span>
  enable</span> =</span> true</span>;</span></span>
  onActivation</span>.</span>cleanup</span> =</span> "</span>zap</span>"</span>;</span></span>
  onActivation</span>.</span>autoUpdate</span> =</span> true</span>;</span></span>
  onActivation</span>.</span>upgrade</span> =</span> true</span>;</span></span>
  brews</span> =</span> [</span> "</span>go</span>"</span> "</span>gh</span>"</span> "</span>lazygit</span>"</span> "</span>grpcurl</span>"</span> .</span>.</span>.</span> ]</span>;</span></span>
  casks</span> =</span> [</span> "</span>ghostty</span>"</span> "</span>zed</span>"</span> "</span>docker-desktop</span>"</span> .</span>.</span>.</span> ]</span>;</span></span>
}</span>;</span></span></code></pre>
That onActivation.cleanup = "zap"</code> line is the important one. It means: if a package is not in this list, remove it. The flake becomes the source of truth. If you brew install</code> something manually, it gets removed on the next rebuild. This forces you to declare everything. At first it felt annoying. Then it felt liberating.</p>
The PATH weekend</a></h2>
This one deserves its own section because it took longer than I'd like to admit.</p>
Nix and Homebrew both want to control what's on your PATH. The Nix daemon needs to be sourced before anything else, but Homebrew's shellenv</code> also modifies PATH. Get the ordering wrong and you end up running the system git</code> instead of Homebrew's, or the Homebrew python</code> instead of pyenv</code>'s. I spent a lot of time staring at echo $PATH</code> output before I landed on this:</p>
programs</span>.</span>zsh</span>.</span>shellInit</span> =</span> ''</span></span>
  if [ -e '/nix/var/nix/profiles/default/etc/profile.d/nix-daemon.sh' ]; then</span></span>
    . '/nix/var/nix/profiles/default/etc/profile.d/nix-daemon.sh'</span></span>
  fi</span></span>
  export PATH="/run/current-system/sw/bin:/nix/var/nix/profiles/default/bin:$PATH"</span></span>
''</span>;</span></span></code></pre>
Nix paths first, then Homebrew via shellenv</code>, then user paths. Simple in retrospect. Not simple at 2am.</p>
Where it got fun</a></h2>
Once the foundation was solid, I started pulling in everything I used to configure manually. Keyboard remapping in early 2026 (Caps Lock to Escape, because life is too short for Caps Lock). File associations with duti</code> shortly after (Zed as default editor for 38 file types). And the one that made me irrationally happy: macOS defaults.</p>
system</span>.</span>defaults</span> =</span> {</span></span>
  dock</span> =</span> {</span></span>
    autohide</span> =</span> true</span>;</span></span>
    autohide-delay</span> =</span> 0</span>.</span>0</span>;</span></span>
    autohide-time-modifier</span> =</span> 0</span>.</span>15</span>;</span></span>
    show-recents</span> =</span> false</span>;</span></span>
    tilesize</span> =</span> 60</span>;</span></span>
  }</span>;</span></span>
  NSGlobalDomain</span> =</span> {</span></span>
    AppleInterfaceStyle</span> =</span> "</span>Dark</span>"</span>;</span></span>
    InitialKeyRepeat</span> =</span> 14</span>;</span></span>
    KeyRepeat</span> =</span> 1</span>;</span></span>
    ApplePressAndHoldEnabled</span> =</span> false</span>;</span></span>
    NSAutomaticCapitalizationEnabled</span> =</span> false</span>;</span></span>
    NSAutomaticSpellingCorrectionEnabled</span> =</span> false</span>;</span></span>
  }</span>;</span></span>
}</span>;</span></span></code></pre>
My dock animation speed used to get reset every macOS update. I'd forget, notice it three days later, Google the defaults write</code> command, run it, forget it again. Now make rebuild</code> handles it. Forever.</p>
Security went in too. Firewall with stealth mode, Touch ID for sudo, GPG signing on all commits. All in the flake, all reproducible.</p>
networking</span>.</span>applicationFirewall</span> =</span> {</span></span>
  enable</span> =</span> true</span>;</span></span>
  enableStealthMode</span> =</span> true</span>;</span></span>
}</span>;</span></span>
security</span>.</span>pam</span>.</span>services</span>.</span>sudo_local</span>.</span>touchIdAuth</span> =</span> true</span>;</span></span></code></pre>The daemon problem</a></h2>
I need to be honest about this because no one else seems to talk about it: the Nix daemon on macOS is flaky. After system updates, sleep/wake cycles, or sometimes for no apparent reason, it just stops responding. nix-store --version</code> hangs. Everything breaks.</p>
I got tired of debugging this manually, so I wrote a script that handles both Determinate Systems and standard Nix installations:</p>
if</span> [</span> -f</span> "</span>/Library/LaunchDaemons/systems.determinate.nix-store.plist</span>"</span> ]</span>;</span> then</span></span>
    sudo</span> launchctl</span> bootout</span> system/systems.determinate.nix-store</span></span>
    sudo</span> launchctl</span> bootstrap</span> system</span> /Library/LaunchDaemons/systems.determinate.nix-store.plist</span></span>
    sudo</span> launchctl</span> bootstrap</span> system</span> /Library/LaunchDaemons/systems.determinate.nix-daemon.plist</span></span>
fi</span></span></code></pre>
The Makefile runs this before every rebuild. It adds about a second. Worth it to never think about the daemon again.</p>
The Homebrew boundary</a></h2>
After a year of trial and error, I learned something I wish someone had told me upfront: don't try to replace Homebrew. Just control it.</p>
Nix is great for pure binaries that work identically on any platform. neovim</code>, ripgrep</code>, jq</code>, tree-sitter</code>. But the moment you need something with macOS-specific compilation (like postgresql@18</code>) or a GUI app (like Ghostty or Zed), Homebrew is just better at it. Fighting that boundary wastes time. The onActivation.cleanup = "zap"</code> pattern is the right answer. Let Homebrew be Homebrew. Just make sure the flake decides what it installs.</p>
I wasted weeks learning this the hard way. You don't have to.</p>
One year later</a></h2>
My dotfiles repo started in January 2021 with vim plugins and a zshrc. Five years later it's a complete, declarative system specification. I've used make rebuild</code> to set up a fresh Mac. Took under 20 minutes, most of that just waiting for downloads.</p>
But honestly, the fresh install scenario almost never happens. The real win is smaller and more frequent. A macOS update breaks something? Rebuild. New project needs a tool? One line, rebuild. Regret it? Rollback. Every change is a commit. Every state is recoverable.</p>
That's what Nix gives you. Not magic. Just a system that remembers what it's supposed to look like, even when you don't.</p>
chukwuanu

A year of Nix on macOS
