Then just install KDE in your Arch install. Or use endeavorOS with KDE, or any other Arch based OS with KDE. Don’t be dismissive of other people’s interests.
I don’t understand why people want immutable. I don’t know all that much about Linux but on my Steamdeck it keeps getting in the way anytime I try to do anything
I personally don’t tinker much with the OS. I want it to stay out of the way and let me do things. In the case of Bazzite, everything I need for gaming is just there and works without me lifting a finger.
I like the safety and simplicity immutables bring.
If I’m doing something out of the ordinary, a temporary container usually suffices.
It’s really made the switch from Windows as a daily driver much easier.
You certainly have to learn new ways of doing things when you want to tinker, but they are basically UNBREAKABLE, which is my main plus point. I’m busy, I need my PC to be reliable. I don’t want to have to troubleshoot stuff just to keep it up and running.
If I had more time I would really enjoy the tinkering, but I don’t so I need my distro just work.
Some people like it, I don’t like and will never mess with it. I do understand why some folks like it. It’s basically for those who want a system that’ll never break to a point where they can’t access their data. I just can’t use it
Immutable is fantastic in theory. Where it falls apart is having to basically rebuild the whole distro every time you want to make a change. It should be there your base distro is immutable, then any extra changes go on an additional mutable layer but that would be difficult to set up. (You’d need a package manager like Nixos or something.)
The big problem with the way ostree works is that installing things has side effects. Every item you install with ostree makes all future items slower to install, including regular os updates. This is a significant flaw in the way they designed it and really makes immutable oses less attractive.
It’s not a flaw. Ostree is a last resort, you should be using containerized software. Layering a package should only be done when strictly necessary and not as the regular way to manage packages. If you need an overtly customized system, you use Nix or universal blue to design your new system declaratively and create your custom image.
Man, I almost want to say “I love it”. Remove the “snap” and the “immutable” and I’m all in.
Almost there 🤏🏽
It’s just Arch with Plasma then…
That is being maintained by the kde team.
There’s KDE Neon already. The whole point of this distribution is the atomic immutable part.
Neon isn’t arch based, which is why this one piqued my interest.
Then just install KDE in your Arch install. Or use endeavorOS with KDE, or any other Arch based OS with KDE. Don’t be dismissive of other people’s interests.
Not being dismissive, just expressing an interest in something different.
I don’t understand why people want immutable. I don’t know all that much about Linux but on my Steamdeck it keeps getting in the way anytime I try to do anything
I personally don’t tinker much with the OS. I want it to stay out of the way and let me do things. In the case of Bazzite, everything I need for gaming is just there and works without me lifting a finger.
I like the safety and simplicity immutables bring.
If I’m doing something out of the ordinary, a temporary container usually suffices.
It’s really made the switch from Windows as a daily driver much easier.
You certainly have to learn new ways of doing things when you want to tinker, but they are basically UNBREAKABLE, which is my main plus point. I’m busy, I need my PC to be reliable. I don’t want to have to troubleshoot stuff just to keep it up and running.
If I had more time I would really enjoy the tinkering, but I don’t so I need my distro just work.
Some people like it, I don’t like and will never mess with it. I do understand why some folks like it. It’s basically for those who want a system that’ll never break to a point where they can’t access their data. I just can’t use it
Immutable is fantastic in theory. Where it falls apart is having to basically rebuild the whole distro every time you want to make a change. It should be there your base distro is immutable, then any extra changes go on an additional mutable layer but that would be difficult to set up. (You’d need a package manager like Nixos or something.)
That is exactly how OsTree and other layering solutions work. Only Nix requires a whole distro rebuild.
And even then with
nixos-rebuild switchyou won’t really notice that you’re “rebuilding” anythingIt isn’t, though. Package layering modifies the install itself. See: https://docs.fedoraproject.org/en-US/fedora-silverblue/getting-started/#_flatpak_command_line
The big problem with the way ostree works is that installing things has side effects. Every item you install with ostree makes all future items slower to install, including regular os updates. This is a significant flaw in the way they designed it and really makes immutable oses less attractive.
It’s not a flaw. Ostree is a last resort, you should be using containerized software. Layering a package should only be done when strictly necessary and not as the regular way to manage packages. If you need an overtly customized system, you use Nix or universal blue to design your new system declaratively and create your custom image.