21–30 of 50 posts
i feel very alienated by the guix developers due to the way they are betraying the gnu leadership. This is sad because it is such a nice and important project. But I cannot easily separate the work from the people who did it.
> they are betraying the gnu leadership What do you mean?
I think the difference between NixOS and Guix, excluding the language of choice of course, is that NixOS has the community to make it work. For example, I had a issue last night that I opened a issue in GitHub, and in a few hours the maintainer of the problematic package answered me and the problem was fixed.
Earlier quoted context omitted.
> they are betraying the gnu leadership What do you mean?
My guess is that they're referring to the open letter from people working on many GNU projects calling for Stallman to resign.
https://guix.gnu.org/blog/2019/joint-statement-on-the-gnu-pr...
I don't know that much about Guix, other than "super-free Nix with scheme" (and the article wasn't particularly illuminating other than boiling down to "Guix isn't really ready for most users right now"), but it's neat that there's momentum in the declarative OS-space. I hope that both Guix and NixOS keep growing and that more people start switching. After switching to NixOS, I'd find it very frustrating to go back t…
I don't know that much about Guix, other than "super-free Nix with scheme" (and the article wasn't particularly illuminating other than boiling down to "Guix isn't really ready for most users right now"), but it's neat that there's momentum in the declarative OS-space. I hope that both Guix and NixOS keep growing and that more people start switching. After switching to NixOS, I'd find it very frustrating to go back t…
> and the article wasn't particularly illuminating other than boiling down to "..."
Yeah, I usually don't like writing these kinds of things. When reading about a distribution, especially a new and interesting one, one (or at least I) tend to forget what could go wrong. This text (I intentionally avoid using the word "article") is a reminder to stop, think and consider if one is up for the challenge. As in my case university just started last week, my conclusion was I didn't have the time.
> It's interesting that Guix uses scheme instead of a home-baked configuration language like NixOS.
I consider that to be one of Guix selling points. An established language, with many independent libraries make it a joy to work with (assuming a set up environment). From what I head, that's not really the case with Nix, although I understand the lure of a type system.
Thank you for shedding light on a distro I didn't know existed! One tip: The contrast on your code blocks is terrible with white text against a light white background. Consider changing the `background` of line 3 of style.css to `purple`, `darkorange`, or some other dark color.
I'll try to fix it as soon as possible.
> For a new package to be accepted into the [Debian] stable branch, it has to pass a number of days without any bug reports. Um, that's not even remotely close to what the actual stable inclusion rules look like.
It is close to the rules for a package to get included into 'testing' from unstable, they must have gotten the branches mixed up.
I mixed the two up, will fix.
I don't know that much about Guix, other than "super-free Nix with scheme" (and the article wasn't particularly illuminating other than boiling down to "Guix isn't really ready for most users right now"), but it's neat that there's momentum in the declarative OS-space. I hope that both Guix and NixOS keep growing and that more people start switching. After switching to NixOS, I'd find it very frustrating to go back t…
I don't know that much about Guix, other than "super-free Nix with scheme" (and the article wasn't particularly illuminating other than boiling down to "Guix isn't really ready for most users right now"), but it's neat that there's momentum in the declarative OS-space. I hope that both Guix and NixOS keep growing and that more people start switching. After switching to NixOS, I'd find it very frustrating to go back t…
I'm hoping that maybe Flakes[1] will help ease the issue/pull request situation by letting some of the namespaces move out of the main repository. [1] https://github.com/NixOS/rfcs/pull/49
As a long time contributor, I'd much, much rather see our bug reporting, triage, and discovery/resolution strategies improve first -- long before going as far as splitting up the mono-repository. That's the part that's frustrating for users (their reports get lost, forgotten, duplicated) -- not the fact the default set merely has a lot of packages.
I understand and perhaps admire the GNU project's insistence on being blob-free, but that also means Guix won't run out of the box on 99% of all people's computers. The options are buy (old) hardware that doesn't need blobs (which sometimes isn't even possible), or compile the default kernel to include the binary firmware yourself (which the Guix documentation won't explain for ideological reasons). Both of these wil…
True for workstations, but most services are running on VMs these days. OS shouldn't need blobs to run on VMs.