I’m wondering what the current favorite distros are besides the most popular ones like Arch, Debian and Fedora.
You must log in or register to comment.
OpenSUSE Tumbleweed has been my desktop home for the last year. It’s very up to date, yet it’s somehow solid and reliable despite sometimes receiving hundreds of updates per week. And if anything goes wrong with an update you can easily roll back to a BTRFS snapshot. It has a good repository supplemented by Flatpaks, and I haven’t had any problems finding software, yet it’s not a hassle like some other cutting-edge distros. It uses KDE Plasma by default, which I consider a plus. I came to it from Mint, which was my go-to distro for a long time, but I enjoy Tumbleweed more for its up-to-dateness and configurability, and I have (surprisingly) encountered more software gaps on Mint.
deleted by creator
Opensuse TW
deleted by creator
I’ve been using Opensuse since it was called SuSE. Tumbleweed is great.
Can it still be a favourite if I haven’t touched it in a decade? I still love Gentoo but I have enough shiny things to burn up my time.
Same! I’m on Ubuntu and Pop these days but I fondly remember my old distcc build cluster…
Portage is still far and away my favorite package manager.
Hahaha same on the distcc cluster. It was a rare proud moment for me many years ago. I rememeber when I got the cross compiling working it felt like magic. Good times.
OpenSUSe. Tumbleweed as a rolling bistro is amazingly stable, yast is nice, and it all just works great. Leap for the servers, and things are solid.
I, too, get my coffee from the rolling bistro.
Loool I’ll leave it
Same. Tumbleweed here. All the benefits of the rpm ecosystem but with less hassle and more updates
OpenSUSE for me too.
I also switched family & friends to Thimbleweed (since a bit too snappy Ubuntu) & it’s been great.
I should think so too. A Thimbleweed sounds an excellent plant for an Evil_Shrubbery.
My evil plans have been discovered!!
Regardless the evil plant army must grow. Rolling thimbleweeds are usually our scouts and assassins (rarely kamikaze when on fire, looks cool tho).
What I’m saying is that you better be on the lookout, maybe hide if you see a thimbleweed with a gun or knife.
I’m enjoying what Nix does. That said, the learning curve is very steep, and the documentation is very inconsistent and usually poor.
The repositories for both nixpkgs and nixos are absolutely colossal, which is a huge plus, but their configurations are not listed on the same page, and it can lead to a lot of confusion. Unlike Arch’s PKGBUILD, which practically tell the build system exactly what to do, you’ll have to learn the structure of current configuration files, or the more recent flake system, to setup things how you like.
Maybe I’ll wait until things aren’t a mess
Its actually not that bad. A few google searches on how to setup config files and going to https://search.nixos.org/packages to show you what info to fill in in the NixOS configuration is all you do.
And, even more importantly, https://search.nixos.org/options to figure out which options to set. Always search for options first. “Installing” something by just adding the package to systemPackages etc. is usually the correct thing to do for end-user applications but not for “system things” such as services.
I recently had the same thoughts but was Ted to try nonetheless. Asked for some beginner friendly resources here on lemmy a little while back. Might be to further help for some 😊
Do you mean http://search.nixos.org/packages Because that has config info on the page of the listed package. Unless I am misunderstanding what you meant by their configurations?
That’s technically correct. The “NixOS configuration” tab is sufficient to just install something, however out of ever package I’ve personally used, none of them have listed the available options there. For example: this theme, and what the extra options are
the documentation is very inconsistent and usually poor.
So many excellent projects are crippled by having little but reference docs and scant, over abstracted descriptions.
Damn Small Linux was a favorite a long time ago.
PopOS! Is it for me these days.
I’ve started to dip my toes into NixOS. I really love their design concepts.
Damn Small Linux became tiny core linux! it’s still something that’s fun to play around with
OpenSuse tumbleweed
Gentoo. It’s amazingly customisable, easy to configure and write packages for, has an extraordinarily good wiki (and installation instructions), and is always seeing new and active development.
There is also official binary package support for architectures as of recently too, which makes it easy to mix and match compiling from source and binary packages.
+1 for Gentoo - Portage can be fun in a weird way. I’m more of a “just work” type of person though, so I’ve stuck to Arch, but the time I had with Gentoo was pretty great and the new binary package format might bring me back. I do have a 7950X nowadays so I wonder if that’d fly through Gentoo on bare metal.
I discovered this on Lemmy, clearly there is no going back
Wait until you hear about biebian
Another vote for openSUSE Tumbleweed
I’m trying out OpenSUSE Tumbleweed on a few personal servers as I wait for Slowroll, I want to get back to trying to get Gentoo running, and I should check out Guix as a server in a VM.
Gentoo having a binary option should help since I seem to mess up the kernel part of the installation.
I use the bin kernel. I don’t change anything that is kernel level, so the default is fine. It cuts down on updates and install by a lot, but more important is that it’s stable. I personally love gentoo, it’s my favorite and I’ve tried basically everything.
dist-kernel for gentoo is even better. Kernel from source but the distribution give a config that works for most. Then if you still want to change something you can patch it. It is wonderful.
Alpine.
I’m a longtime Arch user, and would have preferred to use Arch on a particular system, but didn’t want to deal with needing to babysit ZFS packages from AUR.
So, I decided to use Alpine after never having tried it before, and ended up sticking with it. Like Arch, it’s both lightweight and has a capable/sensible package manager, which are the main things that are important to me.
I haven’t had any growing pains from Alpine’s use of busybox/musl/openrc, things mostly Just Work!
It will bite you after a while. I remember using alpine in a docker image many years ago and running a python program that needed some modules installed, where one of them required compiling c code. Naturally that didnt work on alpine since its using its own c library. So couldn’t run the python app at all on alpine.
