Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing GNU Guix vs Chakra, the Slant community recommends Chakra for most people. In the question“What are the best Linux distributions for desktops?” Chakra is ranked 76th while GNU Guix is ranked 81st. The most important reason people chose Chakra is:
comes with none GTK apps per default
Specs
Question Ranking
Pros
Pro Can setup a shell which has exactly the defined libraries available
A method which works across languages and provides a reproducible programming environment.
Pro Can always roll back to a safe state
Guix creates new profile generations for each operation. If anything goes wrong, a simple --roll-back gets you immediately back to the previous, working, generation. Because it is a purely functional package management system, generations don't affect each other, so you're back to the exact same state as before : still working.
Pro Can create independent packages
Guix pack creates packages which do not need Guix to be run.
Pro No side effects when building packages
Guix is a purely functional package management system. This means that the act of building a package does not have side effects, such as destructively updating or deleting files that may be used by other packages.
Pro Can build containers right-away, from docker to tarballs
See guix pack --help and here.
Pro Easy to add your own packages
The clean and declarative syntax makes it easy to define new packages by using an existing one as an example.
Pro Doesn't require root privileges
Normal users can install packages on a Guix-enabled system, or even run their own Guix instance if the system isn't Guix-enabled.
Pro Focuses on KDE/Qt Apps
comes with none GTK apps per default
Pro Independent from Arch
its not just another Arch Spin-off
Pro Keeps Gnome apps tidier even than Gnome distros
Cons
Con Updates take a long time
It's gotten better over time but both updating Guix itself and updating the installed packages can take a long time.
Con Cannot handle filetypes that have different semantics across different versions
While the functional approach that Guix takes is great for sandboxing binary artifacts of packages, it seriously lacks any power in handling configuration files or user data. It's difficult to upgrade and downgrade files where semantics and syntax can change between versions.
Con Weak base
Sometimes updates will not execute hooks(full update always misses to run mkinitcpio) so you get an unbootable system.
Con Small development team
The team is very small
Con No real installer
Has no installer just a big bloated LiveCD that gets unpacked to your disk.
Con Pacman
Compared to deb or rpm it takes ages to update the system, it's also very dumb in dependency tracking.
Con Unreliable Servers
The CCR or the community forums are often down or unreachable.
Con Overwrites your default EFI config
It overwrites your default EFI config wich can make you PC unbootable if something goes wrong.
Con Uses systemd
Which is very hard to debug and not a *nix standard.
Con Only available for x86-based CPUs
Con Wont let you install the system to USB drives
Chakras weak installer Calamares does not allow you to install it to a USB drive.
Con Weak update process to a recent release
For example, you can install the Goedel Release and update it to the current release which then fails to boot due to some systemd-errors.
