different distribution fights. Different display manager/desktop environment/window manager users fight.
Why can't they just left (stupid, means user that want a friendly and lagging desktop environment; ignore this word) users to use things like gnome and kde and other desktop environment, they can still use their wm for maximum productivity and performance.
This is a very stupid fight.
Look at the BSDs, OpenBSD users can laugh on FreeBSD for having to support wine, running ia32 binaries on amd64, broken at securelevel 1, having so many extension for ls(1). FreeBSD can laugh on OpenBSD for using giant lock (doesn't take advantage of multiprocessor machine), ...
For example, chromium on OpenBSD use the unveil(2) system call to restrict itself to /tmp and $HOME/Downloads .
Many popular flatpak applications have filesystem=host. This is equal to restrict all filesystem access and then unveil the whole filesystem.
Apps are not updated to support portals for “compatibility” or just lack of maintenance. Flatpak needs to follow their approach if they want to have many apps being supported.
Desktop Linux doesnt have the marketshare to dictate that all apps need to adopt portals. In the meantime, flathub.org has a rating system and verified checks, this is simply not well shown in KDE Discover and not sure about GNOME software.
If they can't even enforce portals, flatpak is a new level of complexity.
That’s a very strict interpretation of the community rules.
I think it is lax: I consider coreutils, busybox, binutils, c compilers, posix, even new distros and package manager and package format and desktop environment that crop up every day are still Linux-related.
software that runs on linux operating systems
There are so much...
Even discord app new versions should be announced here :)?
Kernel discussions are niche enough that you should start a new community called linuxkernel imo.
Oops, that won't exist. (People here like customizing their desktop and share their neofetch rather than talking about the kernel. I'm trying to find gems in this limestone community.)
I doubt whether "debloating" could reduce stability or not. I've never done that and have no intention to do it for my 88 year old grandfather's windows. I'd have strict applocker rules on, though
Why it is unfounded?? The sandbox is still a lie (flatseal is impractical security since it makes you become a security researcher overnight), apps are not properly filesystem-unveiled. But a new level of complexity.
I think it would save you someday, when there is nothing writing in /usr so the writing in /home would not cause much damage. On a system with a huge root partition, an incomplete writing might damage the whole filesystem.
Fsck would be faster. newfs (mkfs) would be faster. I found NetBSD spend so much time when it do newfs a 32G root partition (installing NetBSD in hyper-v).
Also for the /tmp partition, we can use memory filesystem (tmpfs) if we have 4G of RAM or more, instead of physical disk to store things that are cleaned on reboot.
Partitioning have benefits. It is quite easy to set up "modern gnu/linux" since they all use a graphical installer. For sizes you can refer to openbsd's disklabel(8) man page.
It increase stability and security. Not only for enterprise.
Not as restrictive as chromium's unveil.
For home it even restrict to the downloads folder, not accessing the whole home directory.