nixpkgs VS nix-gui

I don't think so. The article is probably intended for the Nix community, so the author doesn't need to convince HN that something is going on. If as an outsider you are interested then you need to look into it yourself, the community has no obligation to make their internal conflicts legible to the outside world.

As an outsider myself, it certainly looks like something is going on as more than 20 Nixpkg maintainers left in a week: https://github.com/NixOS/nixpkgs/issues?q=label%3A%228.has%3...

https://github.com/NixOS/nixpkgs/commits?author=neon-sunset

I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors

For a single file script, nix can make the package management quite easy: https://github.com/NixOS/nixpkgs/blob/master/doc/languages-f...

For example,

```

Yes, Nix doesn't actually ensure that the builds are deterministic. In fact it works just fine if they aren't. There are packages in nixpkgs that aren't reproducible: https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aiss...

I'm not familiar with Bazel, but Nix in it's current form wouldn't have solved this attack. First of all, the standard mkDerivation function calls the same configure; make; make install process that made this attack possible. Nixpkgs regularly pulls in external resources (fetchUrl and friends) that are equally vulnerable to a poisoned release tarball. Checkout the comment on the current xz entry in nixpkgs https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/comp...

NixOS uses a monorepo and I think everyone's love it.

I love being able to easily grep through all the packages source code and there's regularly PRs that harmonizes conventions across many packages.

Nixpkgs doesn't include the packaged software source code, so it's a lot more practical than what Debian is doing.

https://github.com/NixOS/nixpkgs

In this specific case, nix uses fetchFromGitHub to download the source archive, which are generated by GitHub for the specified revision[1]. Arch seems to just download the tarball from the releases page[2].

[1]: https://github.com/NixOS/nixpkgs/blob/3c2fdd0a4e6396fc310a6e...

[2]: https://gitlab.archlinux.org/archlinux/packaging/packages/ib...

This is pretty close https://github.com/nix-gui/nix-gui

Nix based aiming at beginners. If it combines/works with https://github.com/nix-gui/nix-gui, then an amazing distro may be created. It would be user friendly, but also extremely powerful, allowing basically everything to be configured via the gui. Both softwares are alpha state, but I am excited to see what they bring.

Maybe https://github.com/nix-gui/nix-gui? I dunno if it can do userspace config though.

Would it make sense to integrate something like nix gui into this?

I remember when I first started using NixOS, as a confused beginner I tried to find a graphical application to manage and edit my configuration. I stumbled upon Nix-Gui, however, I didn’t really like the look, it crashed a fair amount, and I never really figured out how to use it. That said, their idea and all of the hard work they put into their project inspired me to make a similar application that focuses more on simplicity and ease of use.

I was wondering if you are aware of https://github.com/nix-gui/nix-gui and how your tool compares to it

There is also a GUI in development, hopefully it will help casual users in the future.

There's https://github.com/nix-gui/nix-gui for a gui like experience.

Configuration language usage: Probably a major win for programmers, but a major negative for non-programmers. However, nix-gui has shown that there's potential for gui-based nixos configuration. And this might one day be extended to use as part of the graphical installer. https://discourse.nixos.org/t/why-is-there-no-installer-for-nixos/16644/21. Since nix can be serialized and deserialized to json, there's actually a fair amount of interoperability able to be done to manipulate nix configuration using existing libraries.