209
submitted 2 days ago by TheIPW@lemmy.ml to c/linux@lemmy.ml

Two years into full-time Linux and I’m finally burning the distro-hopping cycle. I fell for the Arch/AUR trap for a while, but I got tired of spending my weekends debugging file manager crashes instead of maintaining my home lab.

Switched back to Fedora, and it’s boring in exactly the way I need it to be. It’s a stable launchpad for my projects, not the project itself.

you are viewing a single comment's thread
view the rest of the comments
[-] esperal@pawb.social 13 points 2 days ago* (last edited 1 day ago)

Yes ! I don't get why debian always seems to be forgotten outside of its server use. I have been running it for 2 years now (homelab, laptop and desktop).

[-] corsicanguppy@lemmy.ca 2 points 22 hours ago

debian always seems to be forgotten outside of its server use

Nah, not even for servers. SLSA and ISO27002. Validation in the other distros is better, and that's night-and-day for server sector.

I worked Unix in 99-06 and there's a reason their Linux offering wasn't debian: that validation hole.

[-] throwaway403@programming.dev 17 points 2 days ago

Beyond none of its branches actually satisfying my preferences, I feel like the way it handles major version upgrades is way too involved. I suppose it makes sense; it's paying back the accumulated debt of a couple years worth of bliss...

Having said that, my experience on Fedora Atomic is (almost) equally blissful without requiring any of that whenever a major version update strikes.

Don't get me wrong; I definitely do believe Debian has its uses on desktop Linux. But I can't shake off the feeling that they're definitely more niche compared to say Fedora.

[-] AdamBomb@lemmy.world 5 points 1 day ago

The upgrade issue is exactly why I don’t like Debian-based distros for my desktop

[-] SusanoStyle@lemmy.ml 8 points 1 day ago* (last edited 1 day ago)

I love Debian, I use it as a desktop and it's installed on all my machines, but it has some problems/quirks that make it hard to recommend it for desktop usage.

First one is that it doesn't have sensible defaults, the OS expects a user who is an admin, one who will configure things to their liking. I would consider this to be a feature, if it weren't for the second problem, the documentation. The documentation is wayy too dated, lots of pages in the wiki haven't been updated since Debian Buster days!

A better recommendation would be probably a Debian derivative like MX Linux. They are more opinionated, but as far as I know, they come with better defaults and offer newer guides, documentation, etc.

[-] IrritableOcelot@beehaw.org 4 points 2 days ago

Debian is nice & boring, but I have had issues with how old its kernel and software versions are. 6.12 isn't too bad for Trixie, but previously it was really terrible. When I was running Bookworm, I ran into plenty of situations where software I was compiling or getting from outside the repos (for niche software), wasn't backwards compatible to the library versions Debian provided.

No hate for Debian, but it just doesn't work for a lot of people. However, these days I would go for Debian over Ubuntu 10 times out of 10.

[-] Mondez@lemdro.id 3 points 1 day ago

That is a release engineering issue on the developers side in my opinion though no less real. Developers targeting Linux should target the current version of big LTS releases like debian and Redhat enterprise if they are serious about compatibility beyond "works on my system"

For the vast majority of computer users I'd says debian is fine since most users hardly step out of the browser these days.

[-] IrritableOcelot@beehaw.org 1 points 20 hours ago

Staying compatible with LTS releases should absolutely be the goal, but that takes work from both sides.

If Debian is applying backported patches to old software (I think the oldest version I saw was 6 years out of support) that generates a nightmare to support for package maintainers. If there are features which are not supported since the version is so old, but there are backported security patches which change the API, the developers would essentially have to maintain a specific version for each LTS distro's specific set of patches, and the number of versions you have to maintain and the length of time you need to maintain them for quickly becomes impossible to manage.

Stable is nice, but you can have stability without being criminally outdated, as Trixie shows. The ideal is to have a stable and up to date distribution.

And yes, most users would be fine due to just being in the browser, but thats true of literally any OS or distro, not specific to this.

[-] Mondez@lemdro.id 1 points 20 hours ago

I don't think back ported security patches should be changing public APIs, are you speaking from actual experience or is that some kind of theoretical problem that might not actually exist or at least isn't the norm?

this post was submitted on 01 Aug 2026
209 points (94.1% liked)

Linux

66782 readers
772 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 7 years ago
MODERATORS