Shatner had the gut, but did you see him use an elevator to get on Jeff's rocket? He climbed the stairs, 7 flights, roughly 70 feet above ground, at 90+ and clinically obese. Was he gasping when he got to the top? Yes. Did he do it? Yes! Did he keep up with the kids half his age? Yes!! Did he complain? No! Did they use a (danny) crane to hoist him up there? No! Could Patrick have done that? I doubt it after watching his performance in Picard. He looked and acted feeble in that. Patrick was thin, but that doesn't mean fit. Shatner was fat, but strong.
I only watched the first season of Picard (and, sadly, didn't like it much), but I got the impression that Stewart was acting feeble. I saw him on TV a few times (Graham Norton, the Oscars, maybe something else) around that time, and he looked and moved way better than he did in the show.
I watched "Boston Legal" because of him. He clearly was enjoying himself, including making snide remarks about himself and making references to Star Trek. I wish him many more happy years.
Guix users can just add the Fearware Guix channel which is just the nonfree firmware and blobbed vanilla Linux kernel, no propietary software it's added, just the necessary firmware to run your hardware (3D Radeon support, Nouveau+reclocking, some audio chipsets, and most of non-ant9k WiFi cards).
That's it.
I used to wonder this same question and weighed guix and nix quite a bit before moving to the nix camp.
Guix on paper really sounds ideal, it feels like a more compelling design, more first principles, it's all scheme, really exciting ideas under the hood. But design intent is not a substitute for the actual user experience. IRL it's too much hassle: weak package coverage, weak ecosystem, a steep learning curve, most stuff will require work because it was designed around systemd.
Now NixOS on the other hand already has an abundance of packages and real adoption. Most setups can probably migrate to nix today with a backup of /home and a competent LLM agent, and things "will just work". I did this recently!
Add to that the NixOS ecosystem where things are fairly simple to setup declaratively and "it just works": disko for partitions, sops-nix for secrets, restic for cloud backups, microvm for light vm's, NixOS anywhere or deploy-rs for deployments (colmena or nixops4 for interconnected nodes even). You can do complex things, and your rig or network could explode and it won't matter cause you can rebuild and deploy to a new/repaired machine in minutes. Your backups could explode and all you'd lose is state.
All that is easy to have in Nix today - I know cause I literally just switched and did most of it with like 0 experience. I migrated my fairly complex setup 1 to 1 and gained a ton of useful stuff in Nix, whereas with Guix it wasn't even possible (I would have to trim or package / translate tons of stuff), nor would it have been easy, and all the cool stuff I gained with nix is either difficult or non-existent on guix, let alone mature.
Thanks for your detailed reply, that was what i was after. I wasn't having a go at Nix or their decision, just wanted to understand the why in the choice. Your two responses have helped explained that.
I agree with Guix, the whole package really appeals to me. I found the same issues between Nix vs Guix, having to do a lot more fiddling to get to where i wanted to be.
Guess next time I will word my statements better :)
That's already the case in determinate-nix. Flakes do have big problems though - try cloning a big data project with GBs of data and see how much you love flakes when it copies it to the store every time you run `nix run .#analysis`.
