Hi Friends!Curious about Nix? Me too. The past few months of exploring it were quite interesting, to say the least. And it still feels like I've barely scratched the surface. [TL;DR] That said, it's already replacing some of my old workflows and I'm really happy discovering it, even while not even using Linux for most of my local work. What’s Nix?Nix is a powerful suite of tools, including a package manager (Nixpkgs), language (Nix DSL), and operating system (NixOS). It provides a robust environment for reproducible and declarative configuration management. Why Should You Care?Developers often struggle with maintaining consistent and reliable development environments. Traditional package managers fall short in managing dependencies and ensuring reproducibility. Think of your local workspace when you build an application requiring Go 1.20 or your old web blog running on Jekyll that only builds on Ruby from 2018 (don’t ask me how I know). On top of these, you may find yourself moving often to new machines where you need your tooling, or to remote servers where having your CLI tools like Tmux or your beloved Neovim with all its plugins would make your life 10X easier. On top of all these, what if I told you there’s a better alternative to your current package manager? Whether your running MacOS or Linux, there’s a different, BETTER way, to build and install packages, and use local CLI tools. Interested? What Most Users DoMany developers rely on package managers like Homebrew on macOS or APT on Linux (yea yea, AUR on Arch, BTW). While these tools manage packages, they often fail to isolate dependencies or ensure consistent environments across different machines. Another way many people use for local environments are docker containers. Building and running them is great at maintaining reproducible environment and sets of tools. HOWEVER, even docker falls short in many places where Nix doesn’t: 1. With a container you’d have to mount the paths you with to work with prior to running. This means, that by default, your local code isn’t exposed to the running container. Every change of path / port / volumes, requires a re-run. 2. There’s a case made for Nix derivations and how they’re far more reliable than Docker layers 3. Lastly, even with the above solved, containers are simply not built to host your local tooling on other machines, remote servers, etc. While it is possible, it’s not built for that and you won’t enjoy doing let, let alone make most of the host around it. In comes NixBefore even going in the big claims Nix makes around reproducibility and package offerings, here’s a killer feature that may be enough for some to start using it today: Nix Shells for One-Off Tooling: Nix allows you to create temporary development shells for one-off tasks without polluting your system. For example, you can run a shell with specific tools like While Are you on a Mac? Run
brew list . Happy with the list you see? I wasn't.
Apt users: apt --installed list . Yum: yum list installed For those on AUR: yum pacman -Qm Reproducible Environments from a Nix File: You can declare a suite of packages in a Nix file to create a reproducible environment. Running Better Packages on macOS: Nix can replace Homebrew or MacPorts on macOS, offering a more reliable package management system. Install packages with precision and avoid the common pitfalls of other package managers. Here’s a better Homebrew drop in the next time you install Tmux: Moreover, MacOS users can enjoy the amazing Nix Darwin project allowing for a full OS configuration using a configuration file that can configure your dock, the finder menu, and even customize the login window all from one config file! Here’s an example from my dotfiles. Moving Towards Nix Flakes: Nix is gradually adopting a new feature called flakes, which offers better dependency management and reproducibility. You can create a flake locally or use remote ones. Here’s how to create a basic flake:
By running If you’re curious, here’s the part of my recent Nix intro video showing modern Nix! All of the above made me switch most of my package management, as well as my way of configuring new machines and backing up my current setup to Nix. I’ve also starting playing with the idea of using it for my dotfiles with home manager but we’ll keep this story for a future post :) Thank you for reading, as always, feel free to reply to this post directly with questions and comments! |
Every once in a while I send hand picked things I've learned. Kind of like your filter to the tech internet. No spam, I promise!
Hi friends, Are you tired of juggling multiple apps for note-taking and writing? Many of us struggle to find a seamless system that combines powerful text editing with effective note organization. While popular note-taking apps offer fancy features, they often fall short for those who prefer a keyboard-centric, or should I say Vim-centric workflow. Most people resort to using dedicated note-taking applications like Obsidian, Notion, or even Apple notes. These tools are great for casual users,...
Hi friends, The Dotfiles Dilemma Ever felt like your computer settings are scattered everywhere? Those pesky dotfiles that control how your programs look and work can be a real headache to manage. The Old Way: Git and Stow Many of us have tried using Git to track changes in our dotfiles. Some even use Stow to create symlinks. But let's be honest – it's not always smooth sailing. Sometimes things don't line up right, and not every program plays nice with this setup. Why Traditional Methods...
Hey friends! Are you tired of juggling countless environment variables across different projects? Do you find yourself constantly tweaking your .zshrc or .bashrc with tokens, api keys or other project-specific variables? Well, I’ve got a game-changer for you! The Problem with Traditional .env Files We’ve all been there. You start a new project, set up a few environment variables in a .env file, and everything’s peachy. But as your project grows, so does your list of variables. Before you know...