Nix at work: FlakeHub Cache and private flakes
determinate.systems
Nix at work: FlakeHub Cache and private flakes
1–10 of 32 posts
Re: Nix at work: FlakeHub Cache and private flakes
#2Re: Nix at work: FlakeHub Cache and private flakes
#3I have honestly avoided NixOS for quite a while because the situation seemed "unstable". I don't particularly care for the complaints brought about by the open letter, I do however worry if a distribution/community is imploding.
Re: Nix at work: FlakeHub Cache and private flakes
#4Has the situation between you guys and the Nix community cooled down yet? I have honestly avoided NixOS for quite a while because the situation seemed "unstable". I don't particularly care for the complaints brought about by the open letter, I do however worry if a distribution/community is imploding.
Regarding the stability of the project: The project and distribution is incredibly vibrant, and not going anywhere. There are tens of thousands of organizations that depend on it every day, and projects that are funded on the time scale of decades. It's here to stay.
Re: Nix at work: FlakeHub Cache and private flakes
#5Re: Nix at work: FlakeHub Cache and private flakes
#6Given the extensive infrastructure you and others are building around flakes in the Nix ecosystem, despite flakes still being experimental, what does the roadmap look like for your efforts, and more broadly for officially establishing flakes??
On Monday, we launched Determinate Nix to help make this promise more real: https://determinate.systems/posts/announcing-determinate-nix.... Note: Determinate Nix is not a fork, it is a downstream. Our plan, and intent, is to keep all our patches sent to the upstream project first.
Re: Nix at work: FlakeHub Cache and private flakes
#7Has the situation between you guys and the Nix community cooled down yet? I have honestly avoided NixOS for quite a while because the situation seemed "unstable". I don't particularly care for the complaints brought about by the open letter, I do however worry if a distribution/community is imploding.
There is a lot of turbulance in the project, but I think a lot of that is a natural result of twenty years of history meeting standout commercial success. Our approach here is to continue our pattern of improving Nix and sending patches upstream. We'll also continue improving the ecosystem around Nix, most of that being open source, and only a couple specific projects being proprietary. Regarding the stability of the…
Re: Nix at work: FlakeHub Cache and private flakes
#8Earlier quoted context omitted.
There is a lot of turbulance in the project, but I think a lot of that is a natural result of twenty years of history meeting standout commercial success. Our approach here is to continue our pattern of improving Nix and sending patches upstream. We'll also continue improving the ecosystem around Nix, most of that being open source, and only a couple specific projects being proprietary. Regarding the stability of the…
As someone who just went back to Arch after using NixOS as my daily driver for more than six months, what's in dire need of improvement is the documentation, the rest of the ecosystem was all right.
1. Reducing the number of moving parts, so there are fewer interfaces that need to be documented and understood ... because they don't exist.
2. Resources like https://zero-to-nix.com/, and https://docs.determinate.systems/.
This is a big lift, though, so anything we do here in the near future will definitely not be enough.