this post was submitted on 04 Oct 2024
36 points (95.0% liked)

Linux

48372 readers
446 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

TLDR: is the amount of time used to switch to these distros worth it? (compared to Debian, Fedora, etc.), or is there a better distro that fits my use case?

I have been using Linux for about 4 years now as my daily driver, distro hopping a lot. I have used PopOS (for a few years), Manjaro, Garuda (for a year or so), KDE Neon, Debian, Linux Mint, Nobara (for some months until I ran into system breaking issues), and lastly EndeavourOS.

Issues I have run into in the past are around the different packaging systems and versioning. The Debian/Fedora based ones seem to be fairly slow to update and so they have out of date packages, which sometimes is ok, but sometimes if they are too out of date I have to compile it from scratch. Also the different packaging systems (like apt, pacman, dnf...) means that depending on what flavor I am currently running there may not be a analogous system or maybe a package will be missing and I end up (once again) having to build it from scratch. On the other side I have Arch Linux based ones, which usually works great (especially having access to the AUR) but I end up spending a lot of time configuring stuff that isn't built in (which is by design I know), or having stuff randomly be broken after an update. (which I suppose is my own fault I should have probably set up btrfs or something). Also some libraries will build/work great out of the box on some distros and be completely unusable on others for no apparent reason.

I looked into Gentoo, NixOS, and Guix SD as possible solutions for my issues. Gentoo because since it seems like I have to compile a lot of my libraries anyways maybe I should use a system where you have to compile everything. NixOS and Guix since it seems they are designed for package management and versioning built into the system which might be exactly what I am looking for.

I am worried about the learning curve of all of these. I don't have a lot of time to mess around with configuring stuff all the time. Ideally I'm looking for a distro that works well with my old-ish hardware (with NVIDIA support unfortunately) where I can sit down, program and/or play games on steam+proton; but it seems like I have to choose between "system is stable but packages are old" and "system and libraries are new but is very unstable. Or if I am using snaps or flatpak its "install 5 things and now you are out of memory" (thanks electron).

Also concerned about both NixOS and Guix since they seem to be designed behind "everything goes through the package manager", which is super cool for making it so the environment is the same, but I am concerned about getting stuff to work if a package doesn't exist or if the library is designed to use like 'pip' or 'bun.sh' or some built in package manager.

Any thoughts about this? any non popular distros that might fit my use case? did I give up on some distro too soon? am I just a confused newb?

you are viewing a single comment's thread
view the rest of the comments
[–] degen@midwest.social 5 points 1 month ago (4 children)

I went from Arch to NixOS, so I can offer a bit there.

You definitely won't want to rely on it until you know a good amount and get comfortable. Things can be made to work, but knowing how to get it done is the main thing most of the time.

Regarding package availability, it's just a matter of a few oddly esoteric incantations and version controlled code, usually. Binaries are another story but still possible, and python is a special case of that.

It has been an annoyance for me, but I've also learned a lot by getting things to work. If you use any niche python stuff you're bound to run into something. A bunch is already packaged and works fine, though. Either way there's a bit of extra nuance, which is more to learn.

You don't have to start with NixOS and can feel it out using nix on any distro. It can be hard to tell if someone will vibe with it. All that said, it could be more than you're looking to get into, but you can ease into it if you're interested.

[–] wewbull@feddit.uk 5 points 1 month ago (2 children)

I feel like Nix is a good deployment platform, whereas Arch is a good development platform.

[–] degen@midwest.social 2 points 1 month ago (1 children)

Generally I agree. It feels kind of shoehorned in when desktop is your goal, like more of an afterthought or side effect of the overall focus.

The main thing I hang on to is the code-specified configuration. I never got into managing dotfiles with arch, but that could be a better solution for many people. Especially along with btrfs, numerous containerization options, and whatnot.

[–] zongor@hexbear.net 2 points 1 month ago

This does make a lot of sense. From what I could tell a lot of devs talk about nixos in the same way that they talk about docker.

load more comments (1 replies)