SoylentNews is people
SoylentNews
from the it's-already-perfect-is-not-the-right-answer dept.
We all know about Microsoft's latest OS, so I won't rehash. A lot of us intensely dislike it, to put it politely. Those of us who can, use other operating systems. This is Soylent, so let's focus on the one that is the most important to us: Linux.
I have been using Windows as my OS since right after Atari times. A few years ago I bought an ARM (ARMHF/ARMv7) netbook and put Lubuntu on it. I had problems with my first Linux experience, mainly in the area of installing software: missing packages in Synaptic, small dependency hells, installing a package at a time by hand, some broken stuff. I put it down mainly to the architecture I have been using, which can't be supported as well as x86-64.
Now, we all know that no software is perfect, and neither is Linux, even though it is now my main OS. We support it in spirit and financially, but there is always room for improvement.
So, the question is: What are your problems with Linux and how can we fix them? How do we better it? Maybe it's filesystems, maybe it's the famous/infamous systemd. Let's have at it.
(Score: 2) by tangomargarine on Thursday February 23 2017, @03:54PM
If it ain't broke, don't fix it!! :)
"Is that really true?" "I just spent the last hour telling you to think for yourself! Didn't you hear anything I said?"
(Score: 1) by purple_cobra on Friday February 24 2017, @11:05AM
There's a lot of truth in that, as most of us will admit. Although I suspect more aimed at businesses, the whole concept of LTS releases is, basically, if it isn't broken then don't fix it. :)
But the problem comes when a later revision of an application has some new feature that you've been waiting for or looks useful, so you install that and it needs a new library, that breaks something else, etc. This is why application containers have the potential to become more popular, so you can install a new version of something without buggering the rest of the system. Takes more disk space, of course, and I suspect more memory, but how many people need to run a lot of application containers at the same time? A hybrid version of that - something to tide people over between LTS releases - is probably how we'll end up; it could be as trivial as an extra repo for your package manager that has the newest versions of the LTS applications as individual containers.
Interesting times.
(Score: 0) by Anonymous Coward on Wednesday March 01 2017, @05:53PM
Funny thing is that the library problem is not really a problem with the libraries directly, but with how distros handle dependencies. You can have multiple versions of the same library installed, and expect the linker to sort them out at runtime based on something called sonames. But distros, in particular those based around RPM, are hung up on there being one canonical version for each package name. Thus if you want to have, say, two minor versions of GTK installed side by side, you have to play telephone with the package names to get the manager to play along.