After reading Developing our position on AI from the Recurse Center, the corresponding entry in my newsletter grew long enough I’ve decided to break it out into a full blog post. Above and beyond its specific findings, I think the post charts a path for a more civil and considered mode of discussion that we should all strive for on the Internet and in our own lives.
I wrote most of this post during the week between Christmas Eve and New Year’s Day when enough people in New York have left the city that it makes it quite difficult not to turn introspective. It’s been a pretty big year for me and for this blog, so I thought it would be fun to take a look back on the year as we all move into the second half of the decade.
Welcome back to the Nix on Mac series! By the end of this post, you’ll be able to fully
configure VSCode through your Nix flake via home-manager, which we set up in part
2. This includes:
/Applications for SpotlightDune: Part Two hit theaters recently, which got me thinking about my own experience reading Dune in the past, what I enjoyed about it, and my own personal headcannon that made this novel more enjoyable for me. And hey, it’s April Cools, so why not put pen to paper here?
In part one of this series we
installed Nix, set up our system configuration with nix-darwin, and installed some
packages at the system level. In this post, we’ll set up
home-manager.
Unlike nix-darwin, home-manager is cross-platform: it works across NixOS, macOS, and
anywhere else Nix can be installed. It was difficult at first for me to understand how
home-manager and nix-darwin should interact. While there is definitely overlap with
what these two Nix libraries can do, nix-darwin is used for managing system-wide
settings and applications: it brings the power of NixOS to the Mac. home-manager on the
other hand is most useful for managing user-level configuration and dotfiles.
By the end of this post we’ll have installed home-manager and used it to set up
configuration for vim, zsh, and git.