TimeSquirrel,
@TimeSquirrel@kbin.social avatar

Not really interested in turning my desktop systems into Android or a game console. That's what immutable OSes with Flatpack (the cartridges) seem like to me. I like having control.

I think it's fine for embedded devices or something like a Steam Deck where an end user just wants to plug it in and play and not learn Bash scripting. But I'm a bit old school when it comes to my desktop.

Nefyedardu,

You don't lose any control, at least not in Silverblue. You are free to edit your base image and layer stuff on top of it if you wish just like any other distro. All it does is create a separate "branch" off of the ostree. It does defeat the purpose of an immutable OS though, the idea is to keep your base system as "clean" as possible so there's less surface area for bugs. But you can do it.

MerryChrysler,

I've been daily driving NixOS(unstable branch, so rolling release) for about a year now and once you get used to it it's really great. The best thing for me is that whenever I need to reinstall or get a new machine I can just fetch my config from github and be up and running within like an hour

Patrick-Haverkamp754,

One thing that kinda bothers me about flatpaks, it kinda centralizes the application repository to flathub.org

SFaulken,
@SFaulken@kbin.social avatar

No, it really doesn't. Anybody is welcome to start their own seperate flatpakrepo. Fedora already does this. Any organization could do the same, if they chose to.

Patrick-Haverkamp754,

most arent so far, where as with, typical rpm or deb repositories there were many

SFaulken,
@SFaulken@kbin.social avatar

Most projects haven't found any value in maintaining their own flatpak repositories. We considered it at one point for openSUSE Aeon/Kalpa, but decided it's un-necessary duplication of work.

optissima,
@optissima@lemmy.world avatar

Federated flatpak repos when

simple,
@simple@kbin.social avatar

deleted_by_author

    •
    skilltheamps,

    it's not that important if you know what you're doing and don't break your distro.

    That may be true for intermediate level users.

    Let's go about it this way: Arch for sure is the mutable distro that requires the least fiddling when using it for many years. Much less than any distro that doesn't roll and/or relies on 3rd party repos could ever achieve. Arch only ever has very small hiccups, almost never actually breaks. And yet, after the hundredst time of upgrading the keyring first, recompiling some AUR package because some library changed under its butt or whatever tiniest annoyance, you grow tired of it.

    After a decade of usage you know all these things, you have explored every nook and cranny of your OS, the excitement for messing about is over. You just want your computer to take care of itself, because there's nothing entertaining/surprising/interesting in it anymore.

    An then an immutable distro becomes very attractive. You get an OS that does its thing, no manual intervention required at all. You can concentrate on the stuff you want/need to do. The OS is not the joyful toy with productivity benefits anymore, just a plain tool. Also here and there you may finally discover some interesting new kinds of bugs or challenges that arise from the new paradigma of containerizing literally everything.

  • Todo
  • Suscrito
  • Moderado
  • Favoritos
  • •
  • random
  • noticiascr
  • linux@kbin.social
  • CostaRica
  • Todos las revistas
    •