4 ms·

Everybody that sold nix to me said the goal was to replace the complicated side effect mess that is our current stack with something simple and pure. As with F

Everybody that sold nix to me said the goal was to replace the complicated side effect mess that is our current stack with something simple and pure. As with FP, eventually, practicality beats purity I guess.

ParetoOptimal 4y ago
> As with FP, eventually, practicality beats purity I guess. Until you can take enough advantage of purity that it's practicality is higher.
- crabbygrabby 4y ago
  Probably not worth it. Not trying to be dismissive but genuinely, it's fine to have side effects and if it saves 1000 hrs of engineering over the life cycle of a project I'd wager it's completely worth it.
  - SuperSandro2000 4y ago
    But the big problem in the end will likely be that you have no idea how reproduce the setup from scratch again
  - rowanG077 4y ago
    The keypoint here is that nix requires a larger up front investment. But once done it will save you 1000 hrs of engineering in the long run. It's absolutely faster to start a project without nix and just start coding. But once you have many deps, multiple developers, ci, multiple environments nix becomes a no brainer.