[linsomniac]

>I haven’t given it a shot in the LLM age

I haven't tried it in almost a year, but using Claude Code for setting up my nix config back then worked amazingly well. I've only dabbled in NixOS, and I'm very tempted to it for my workstation when I reinstall it in the next month.

Given how much Claude Code + Opus have improved in the last year, I'd give it a fighting chance to make a nice Nix config. I'll probably start setting up a spare laptop to get the base configs dialed in before switching over to it.

[linsomniac]

To close the loop, I set up a new nixos machine, and have been using Claude Code today to work on configuring it. I was able to point it at some attempts I made in the past, ask it to modernize the setup using flakes, ask it to install a bunch of software and make a bunch of setup changes, shell setup and aliases, switch over to using sway, etc.

I've been bouncing around different vim setups for a while (lunar, astro), but they all seem needlessly complex. I do have a working astro setup, but I had a lot of problem in the past trying to apply it on Nix. Plus, I'm a fairly minimal vimer in general, so I've always felt like I might be better off doing a simpler setup.

I asked claude code to set up a minimal but modern vim config, but with: treesitter and LSPs (for python, ansible, bash, json, yml), and then adding a few other little quality of life features that I've come to rely on. It did a pretty good job, from the basic testing I've done with it so far.

It feels much more manageable than something like Astro or Lunar vims. Every time I have to upgrade those, it's a bunch of files with variables I can configure to control, but those settings aren't super well documented. The nix setup I've got is almost 700 lines in a "neovim.nix", but everything about it is configured directly in there, which seems a lot more discoverable. Fewer levels of indirection.