4 ms·

I've come across this a few times, it seems to cope very well with all the things I'm abusing Make to do. I'm hesitant to add niche tooling requirements to my p

• rcarmo 4y ago
  Well, let me put it this way: I never use a tool that isn’t bundled with the OS or the runtime I’m developing for, because I don’t want my environment to be a special snowflake (and I develop stuff on Linux and macOS, with essentially the same CLI tools).
  • rgoulter 4y ago
    Using the Nix package manager solves these problems. With nix, all sorts of niche packages are available, so installing just isn't difficult. (& packages nix installed only go in /nix/store, so the filesystem isn't messed up). If you want the same programs (the same version of programs, even) across different Linux distributions, and macOS, nix is the best tool for that. If you're worried about your environment being an unreproducible snowflake, nix's main advertised feature is reproducing package installation. Although, yeah, Nix suffer the same cost of "1 more niche thing to install".
    • kaba0 4y ago
      Direnv is the real QOL improvement. You just add a .envrc file, write a flake.nix file listing your dependencies and anytime you enter a project directory you have every project dependency/tooling instantly available, but they otherwise don’t bother you at all.
  • kaba0 4y ago
    Are you writing everything in sh?