For the past year of software consulting I've been using nix to define the development environments. I had been using flakes, but recently I've been using devenv.sh. Devenv is a system on top of nix that makes creating common dev environment recipes a lot easier. Setting up a language, some dependencies, services… even setting up postgres and ensuring some databases are created is a breeze. There are several other similar nix-based dev-ex systems, but (so far that I can see) devenv is the only one that insists on using nix to configure it. So many others try to give you nix without making you write nix… which is a nice idea but in my limited experience is a handicap. When you just devenv init and check in the resulting files, devenv works great. What I've been working through is "what if you don't want to impose devenv on your whole team?" As a contractor I don't really want to foist my development preferences on everyone else. I can .git/info/exclude the devenv files. However last…
No comments yet. Log in to reply on the Fediverse. Comments will appear here.