2 ms·
The problem with linux is not the desktop itself, but almost the whole of the userspace. First of all, security, or the lack of it. The age-old xkcd is still t
by kaba0 5y ago
The problem with linux is not the desktop itself, but almost the whole of the userspace.
First of all, security, or the lack of it. The age-old xkcd is still true, where an attacker can’t install a video card driver on my laptop, but can encrypt, read, send, record basically everything I actually care about on a desktop, and it doesn’t even have to try (seriously, just hide a bash script wherever you want or append to bashrc). Running everything as the same user when no finer grade authorization is available is simply a no go.
Yeah, there is flatpak but I feel it tries to be two things at once, and not being the best in either of them (package management and sandbox). I think we should not imitate what docker or other OSs do, when we have nix, which is imo a superior solution to the problem and we should embrace it. As for the security, we do have SELinux which works very well for courser authorization (fedora does a decent job at it!), but it should be combined with a supportive capability-based security system a la Android, where new processes run as different user from the actual one, and all IPC should happen through some controlled manner.
My second gripe: why do linux people insist on using C for goddamn everything? And no, I’m not advocating for “rewrite everything in X”, but come on, should gnome’s welcome screen be a C executable, really? Especially knowing that bash scripting (which is even worse than C from a correctness POV in my opinion) is the often used alternative —- meaning that performance is nowhere near an issue as goddamn scratch is faster than bash. So other than pipewire, there really are not many places where such low level control/performance is needed, meaning that Java, C# or the other litany of GCd languages could work perfectly fine, and they would likely even increase productivity/maintainability.