216
Finally done with the distro-hop: My return to Fedora (unknownuniverse.uk)
submitted 1 month ago by to c/linux@lemmy.ml
125 comments fedilink hide all child comments
 

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
[–] 6 points 1 month ago (3 children)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 3 points 1 month ago (2 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 1 month ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 1 month 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?

  • permalink
  • fedilink
  • source
  • parent