Hacker News new | ask | show | jobs
by jamies 609 days ago
I appreciate someone from the project commenting here. I left Nix because it just has too many warts, and unfortunately, they've only increased over time, which is the opposite of what I expected.

- I'd update Nixpkgs, and my build would stop working. The logging was awful, so fixing it took hours.

- The mono repo sounds nice, but selective updates are almost impossible.

- Building our Go project in a Nix package was nearly impossible with private GitHub repos, so we moved on.

- Bash scripts never work because binaries are never where they should be in Linux.

I could go on, but my experience with Nix and NixOS left me with significant scars. I’m hopeful that someone will eventually create a more user-friendly deterministic OS.

2 comments

> - Building our Go project in a Nix package was nearly impossible with private GitHub repos, so we moved on.

Yes. This is a nightmare, and is the literal step-one problem FlakeHub is designed to solve.

Regarding the monorepo causing big-bang updates that broke all your stuff: continued, strong, agreement. I think as nixpkgs continues to grow, and usage grows, we'll see a wider adoption of flakes from a pure "how do we all work together?" perspective. That's the flip side of FlakeHub's initial concept.

Please keep at it! Doing what GitHub did for Git is a real opportunity I think for Nix. We'll be keeping an eye on Determinate's work...
Thank you, we will! =). I think there is a lot of opportunity here around a cohesive workflow around Nix. That is a big part about what I was consulting on for so many years.

Maybe check out our demo on our home page: https://determinate.systems/ -- you might like it.

Not sure if you know this, but this is the way to add dependencies to bash scripts:

https://nixos.wiki/wiki/Nix-shell_shebang

It should add everything to $PATH, so unless you've got hardcoded bin paths, there shouldn't be any problems.