nawordar

All of these distros strive to solve the problem with having multiple versions of libraries and programs coexisting without conflicts, but Gobo took a different approach. What Gobo doesn't do is the declarative system configuration. In Nix you don't need to worry about breaking your system because you can easily restore the previous version of your config. In traditional distros you would need to set up package manager hooks to make snapshots and create snapshots manually every time before changing something in /etc

Well, the configuration and state in both cases is all over the place. I admit that since the move to push program directories to /usr and the XDG share/config directories the problem has been largely solved. I only shared my perception when I was learning Linux, which was right after Mandriva came out

When switching from Windows, it was very confusing to me, that program files where all over the place. It was before (almost) every distro switched to the /usr directory, so it was even worse than it is now. Even now, when I understand more about Linux than before, I still prefer the Windows way.

I think that this hierarchy is nice for people moving from Windows, but experienced enough that they could understand the docs and tweak the OS.

I was actually surprised that this distro was designed with more experienced people in mind, I thought it was for beginners.

First Amarok 3, now this‽

Edit: The previous release was four years ago? I was pretty sure it was abandoned earlier

There was the Linux Standard Base project, but there were multiple issues with it and finally it got abandoned. Some distributions still have a /etc/lsb-release file for compatibility.

People thought the same about JVM

*Mastodon

I'm wondering about that too and I think that this question deserves another thread. Maybe that's because, as there are no (or are there?) PCs with other architectures than x86, vendors don't see a need for standards like device discovery and UEFI.

Can you make a screenshot?

I didn't know about the systemd-run command. Do you use it to save the command log? I created a script conveniently named x which opens a file in a default app, in the background, so I can still use the terminal. But then I had the problem with handling logs and this sounds like a perfect solution. Gonna try it today.

As for the alias, I wanted to create a pacman-like interface for systemctl, so the commands would be much shorter, but never finished it. For example, sctl -Eun unit would be equal to sysyemctl enable --user --now unit

Can you calm down a bit?