- cross-posted to:
- memes@sopuli.xyz
- cross-posted to:
- memes@sopuli.xyz
You must log in or register to comment.
Not if they keep fuckin around
systemd-kerneldsystemd/wayland/snap/gnome/uutils/linux
reblog to give stallman a heart attack
Grrrr snap
ngl this sounds awefully acurate ;~;
I wait for the day that systemd unifies all /etc config file and the .* config files into one easy to use service that stores the configurations in one efficient central binary file with a tree structure for the values and thus maintains consistency over all applications, is easy to backup and overall makes life much better for developers and users alike.
Basically nixos*
*with home manager and a .conf flake
Wow I’d reguster for that right away 😉
is that a Windows Registry joke?
For desktop/app level stuff this is already the case with DConf, so I guess the challenge would just be to extend this into the kernel/services how
Avoiding round trips and context switches is desirable in itself, but the real advantage[citation needed] comes from allowing the I/O scheduler in the kernel to do a better job by saturating it with requests coming from all of the applications trying to read their keys (as opposed to a common configuration server serially requesting a single key at a time).
Having all of the keys in a single compact binary format also avoids the intense fragmentation problems currently experienced by the tree-of-directories-of-xml-files approach
https://en.wikipedia.org/wiki/Dconf
I didn’t know.
Ideally stores/spits them out as JSON. Also for the kernel please.
Am I having a stroke or are you intentionally describing nixos
Idk I found its config language kinda confusing. JSON is stupidly simple
Admittedly it is pretty confusing, but its spec describes it as “json with functions”, and once you get a handle on the recursive aspect of it (and that it kinda smushes multiple imported jsons together), its not too bad.
Stupid useful too
Systemd can get in the bin
😨
@gary_host_laptop I mean thats not wrong.
