

CIA Propagandist, Concerned mother, Innocenarestifarianist
I’d want a registry that was compartmentalized meaning each app gets an area to store its own configuration and the apps can only modify their own settings (without root permissions).
Apps should never be expected to modify system settings directly but only through system calls.
Some Linux packages achieve this kind of behavior by adding an additional user which owns their configuration directories. That always felt hacky to me.
A centralized place to store settings (e.g. the registery) isn’t a bad idea in and of itself.
I was watching a recording of Jeopardy (captured via antenna) on my private media server. This was not a recording of a recent episode. One of the answers was a band I’ve never heard of. The next day Pandora played a song by that band.
#Prison Labor Is Not Actually Used
Desktop Environments are decoupled from the underlying system. It makes switching DEs very easy but integration sucks.
I needed to flush dns on my Ubuntu machine. I googled it found a command for an older version. But of course the underlying stuff changed since then and that command doesn’t exist anymore.
The command to flush dns on Windows has been the same for decades. On Linux half the stuff I learn is going to be obsolete in a couple of years and that knowledge can’t be carried over to other Distros because they do it differently.
I also had to manually build and install a driver for a very common realtek wifi chipset that is not even new.
Ain’t nobody got time for that
They essentially would just need to develop their own Wine