After years of Manjaro (and I still use it on most of my computers), I’m trying out Nobara KDE to see how it keeps up for gaming. It has a number of optimizations that Glorious Eggroll has compiled and seems pretty fast compared to Manjaro on the same hardware. I imagine I could do all the changes on Manjaro, but I also wanted to see how Fedora runs these days, it’s been a long time since I used it on the daily.
I was on a 5Mbit connection until recently, so a lot of flatpaks being 1GB+ was frustrating (especially when their native packages were <100MB). And I was using a 250GB SSD, which filled up rather quickly.
And it turns out I wasn’t a fan of the sandboxing aspect. In theory it should be a good thing, but turned out to be frustrating.
It looks nice in the screenshots, but it charges $40 for “premium” which is pretty much the same as the free one, besides it having a few extra themes, and some “professional creative software” and stuff (free software that they are bundling in, and acting as if it’s exclusive to Zorin or something)
They also have an IT management tool called Zorin Grid that has said “coming soon” for years now
Most services just need the init system to start, stop and monitor them. There’s no special integration needed for each of them beyond running a command, monitoring the PID, and killing the PID when it’s time to stop.
If you mean the special integration of docker and podman with systemd, first of all that’s only required in rootless mode and not everybody runs rootless (most users probably run root docker). In rootless mode you have to manage each container individually as if it were a standalone service instead of just managing docker. Basically you have to integrate each container into the init system, whatever that is. There are some tools that make it easier to with podman+systemd because they write the systemd units for you but you can do it with any init system. The distro mostly doesn’t care because you have to do the work not them.
It’s easier to think about Linux on the context of what an individual application needs to run. Pretty much everything you do will have these components.
configuration
an executable
a communication mechanism (dbus, networking, web server, etc)
something that decides if the application runs or not (systemd, monit, docker/docker compose, kubernetes scheduler, or you as the user)
a way of accepting input (keyboard and mouse, web requests, database queries, etc)
a way of delivering an output (logging to unique log files, through syslog, or to stdout/stderr, showing something on a screen, playing a sound, returning a message to the client, etc)
storage (optional)
some cpu and memory capacity
That’s really it. If something isn’t working, it’s pretty much exclusively going to fall into one of those categories. What that means is going to vary significantly from app to app but understanding this is how literally everything works makes the troubleshooting process a lot easier.
The .config folders have important files, like git config. With that being the exception, most of my config files are empty. I have the most Vanilla GNOME setup. My setup is so vanilla, it is also missing the contrast hi-color logos, which is added by default in Fedora in multiple applications, like Firefox or Inkscape.
A biggie you miss is the toolchain: the compiler/binutils/linux-headers/libc/libstdc++ combination. The libc and usually libstdc++ are key components of any install. The other parts usually don't make it to non-dev-desktops, but the distro couldn't be made without them, so they're virtually always available as packages.
Only exception is if the entire distro is cross-compiled or it's made exclusively for containers, but those kinds of special distros break every rule imaginable anyway. Some might not even ship a bootloader or a Linux kernel by themselves.
Tiling addons. I like having a full DE, but I also want tiling, so Pop!_Shell on GNOME and Polonium on KDE are invaluable (and yes, COSMIC looks really promising).
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.