The joke has been lost because the drive's technology is ill-suited for permament storage.
If only we had a hard drive...
Sonotsugipaa
joined 2 years ago
Deliver Hope ...
Nah, it's just that /proc is incorrect - it contains information about running processes, as well as kernel data structures as visible by the process reading them.
Wdym? flamingo_pinyata's explaination was quite useful, I wish somebody had told me that long ago and it's still going to let me save so much time.
thing is, packages probably use /opt because they don’t understand /usr/local…
Indeed it is, it's the same with \~/.config and \~/.local/share.
... and ~/.var.
IMO /opt is the most egregious - /mnt is (as far as I could gather) used as a place for secondary mountpoints, which somewhat fits the original purpose; /usr/lib and /usr/share (and /var equivalents) are perhaps a bit ambiguously used; the way many applications use ~/.config and ~/.local/share infuriates me, but they do kinda do store similar data.
/opt on the other hand is just /usr/local on meth.
I've used Windows for a bit more than a decade, and I only found out its VFS is case-insensitive (by default) after I fully ditched the OS, when a bunch of Electron applications created directories with different cases - nothing ever broke because of it, save for a single Godot game.
Personally, I think case-insensitivity seldom makes sense, though I'm also aware that not everyone [knows how / is able] to properly operate a keyboard.
It feels like /opt 's official meaning is completely lost on developers/packagers (depending on who's at fault), every single directory in my /opt belongs to standalone software that should just be put into either /usr/lib or /usr/share with some symlinks or scripts into /usr/bin.
Don't