budgie-extras VS nixpkgs

I like Ubuntu Budgie. 6th year on it. https://ubuntubudgie.org/

My experience has been that Ubuntu's Gnome DE is somewhat less suitable to older computers than Ubuntu "official flavors" with lighter DE's -- Ubuntu Budgie (Budgie DE), Kubuntu (KDE Plasma DE), Ubuntu MATE (MATE DE), and Xubuntu (XFCE DE) -- all of which use somewhat less resources than the Gnome DE.

If you were a fan of Windows 7 - install Ubuntu Budgie. I have been running it since Windows 7 and it is rock solid.

I recommend two official Ubuntu flavors to friends contemplating migrating from Windows 10 to Linux -- Ubuntu Budgie (Budgie DE) and Kubuntu (KDE Plasma DE).

In terms of distros that will help facilitate the migration from Windows, I would suggest either Ubuntu Budgie or Kubuntu.

Take a look at Ubuntu Budgie 22.04 LTS and Kubuntu 22.04 LTS, two official flavors of Ubuntu that give you the stability of Ubuntu 22.04 LTS and a good looking, very functional desktop environment. I have used both extensively and can vouch for them. My use case is similar to yours -- lots of internet/browser work, occasional word processing, spreadsheet and file work.

Consider looking at several of the Ubuntu official flavors -- Kubuntu (Plasma DE), Ubuntu Budgie (Budgie DE), Xubuntu (XFCE), Ubuntu MATE (MATE DE). I wouldn't bother with Lubuntu (LXQT DE) unless you need a lightweight distro, because the LXQT DE is not as mainstream or well-supported as the others.

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...