Linux

48143 readers

720 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

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

What features would I be losing if I switched to GNOME? (self.linux)

submitted 6 months ago by tester1121 to c/[email protected]

29 comments fedilink hide all child comments

I don't mean for this to become a KDE vs GNOME post. I'm looking at switching to Fedora (because Arch is a pain), and it seems that GNOME is more supported. I use KDE on Arch. What features would I be losing if I were to switch? (ex: toolbar management, KRunner, etc.)

you are viewing a single comment's thread
view the rest of the comments

[–] Para_lyzed 2 points 6 months ago

It is certainly helpful in preventing issues caused by packages updating, as the whole base image should remain consistent (and you could always just roll back to the previous update from grub if necessary and revert a commit that broke your system). Since you were using Arch, I made a baseless assumption that you would want the ability to modify the root filesystem for configuration, but it was a baseless assumption, so if that is not the case, then atomic distros are great for users that don't want to tweak tiny things in root directories like /usr. Granted, you can still overlay stuff if you wanted, so it's not as if you couldn't tweak stuff in immutable directories, it just requires a bit more work to do on atomic distros.

If what you're looking for is a standard desktop KDE experience with a distro that is more resistant to breakage, I'd highly recommend Kinoite. It requires a bit of learning, but not a whole lot. For instance, the typical order of priority for installing packages is flatpak (mostly GUI stuff) > toolbox (terminal-based packages like neovim that aren't already installed) > overlay with rpm-ostree (basically the equivalent of installing through your package manager). The fewer overlays you have, the better your protection from spontaneous breakage is. Of course, there are packages you will have to overlay depending on the situation (like the proprietary Nvidia drivers), but almost everything I need was available as either a flatpak or was practical to install in toolbox (basically a containerized mutable root that lets you install stuff with dnf instead of rpm-ostree). You can add aliases to your .bashrc so you don't have to type "toolbox run " every time, as well. Just be aware that packages installed in toolbox live in a container, and they aren't intended to be able to break out of the container (so if you open a terminal in neovim, which is installed in a toolbox container, it will open a shell inside the container, not on your host). Containers can access your home directory and a variety of different directories in your system, so this often isn't an issue, it's just something to keep in mind (for instance, you can't enable systemd services on your host from inside a terminal).