I use Nix for every project once it grows enough for me to have to pin a directory. And sometimes sooner. I don't know it that well but I've picked up on desig

I use Nix for every project once it grows enough for me to have to pin a directory. And sometimes sooner. I don't know it that well but I've picked up on design patterns, use the repl to figure stuff out, write small abstractions when necessary..and it works pretty great. And the gains grow as my dependencies become polyglot (even C + another language like Haskell..but when you add compile-to-JS, static asset generation into the mix it's amazing) Yeah it's hard to learn. No denying it. But every other "alternative" I've found doesn't actually approach it. So I've kind of gotten sick of reading about "alternatives" because it always feels like they don't actually solve the problem Nix solves. I always end up using the alternative+Nix. Classic example of this is the Haskell stack build tool. I could've bemoaned complexity and various capitalist criticisms when I first ran into it at a job. But I'm so much better off for not.