The Linux ecosystem is vast and diverse, offering a multitude of distributions to suit every need and preference. With hundreds of distros to choose from, it’s a pity that most are rarely mentioned while the popular ones are constantly being regurgitated.
This thread aims to celebrate this diversity and shine a light on smaller projects with passionate developers. I invite you to pitch your favorite underappreciated distro and share your experiences with those lesser-known Linux distributions that deserve more attention.
While there are no strict rules or banlists, I encourage you to focus on truly niche or exotic distributions rather than the more commonly discussed ones. Consider touching upon what makes your chosen distro unique:
- What features or philosophies set it apart?
- Why do you favor it over other distros, including the popular ones? (Beyond “It just works.”)
- In what situations would you recommend it to others?
Whether it’s a specialized distro for a particular use case or a general-purpose OS with a unique twist, let’s explore the road less traveled in the Linux landscape. Your insights could introduce fellow enthusiasts to their next favorite distribution!
In NixOS there’s a bot that automatically bumps versions
The NixOS ecosystem while maybe sometimes both chaotic and heavily centralized just seems miles ahead of what Guix System has to offer unfortunately; nix is a weird language (I’m not qualified to rate it but people have called it a bad DSL), but it does the job, and there were some factors that ruled out Guix System for me. Secure Boot support was one of them, which NixOS doesn’t support “natively”, but there is Lanzaboote. For better or for worse this kind of forced me to look into flakes very early.
Thanks for the info, although versioning afaik not the thing that keeps it behind. There are tools to import the necessary packages with ‘guix import crate’. It automatically selects the necessary packages.
Difficulties arise when Cargo.toml for example uses git as source. Then you have to pull and write specifications for not a standard package. The build system is isolated and cannot download anything off the internet.
So what nix does is it hashes the inputs, so git still works even immutably if the hash matches
Does nix require the exact commit be written out for the package, or does it generate a hash during the build taking the newest git commit?
You need to write the hash in the package, so it requires the exact commit