at some point in the 00s i trained myself out of calling filesystem directories "folders" because nerd people dunked on you as a dumb windows/mac user if you said it. i've spent the best part of a decade trying to go back to 'folders' because its just much better isnt it. its nicer. and also twice as quick to say
the problem with the unix-style filesystem layout is while 50% of people think it's the right way up, 50% of people think that it's upside down, and instead of having folders for each thing a computer does, and a folder for each program within that folder if it wants to do that thing, we should just have a folder for each program like on windows or something you'd put into /opt, with its own subfolders for each thing it does. i am one of those people im afraid
the fact that docker and app images and snap and the macOS .app format and so on seem to exist, to the best of my knowledge, is that that % of developers just go "oh that's not nice is it, aesthetically, i mean, maybe technically too, lets try to put another layer of abstraction on all these files all over the place and at least get all the files into one place"
personally i like the monolithic application installation approach because it allows you to delete an entire piece of software just by deleting the folder it's in. that's great! i love that. i also love the amiga file-extensions-before-names thing, because it lets you easily sort files by type by sorting them alphabetically. both of these are The Opposite of Elegant Thus Somehow Elegant
the serendipitous origin of dotfiles in unix is another Opposite Of Elegant Thus Somehow Elegant fwiw
the only real compromise to fix it is to use a tag-based file system, or just have everything on the computer inside a database so there is no one true hierarchical arrangement of the data, which would be technically cool but ultimately probably satisfy nobody do nothing but annoy both sides even more, and presumably conflict would then erupt over tagging terminology and database schemas
as someone who wants to like, install and configure something, or use or make software, it's such a pain having all of these different places i'm supposed to look for/install/write to in specific ways, and just seems to make everything take ages, because i'm always doing a breadth-first search over the filesystem. but i suppose if i was a unix sysadmin 35 years ago, grumbling under my breath, lighting a cigarette and trying to drill down into /var/log, it'd be handy to have it arranged this way
@jk Monolithic applications that exist not only in the disk but also in memory in the registry whose commands, structure, and purpose are so far from elegant that it contains mockery of a member of the team who was afraid of bees(hence hives), and the ultimate end of each windows installation when even a single bit is corrupted :3
@jk someone proposes this about once a decade or so and it invariably vanishes without a trace inside of six months
@jk Don’t worry now we have containers, so we can give each app it’s own entire tree to itself!
@jk kind of a centrist on this one; while I agree it doesn't make sense to spread complicated apps in a thin paste all over the filesystem I also get the utility of chucking all the important little programs into /bin or whatever
@jk /usr can fuck off though, who really thinks that's still a good idea
@jk "oh we ran out of space on a drive one time in 197X guess literally the entire planet will have to live with our shitty workaround forever" ffs
@jk I think a pretty good argument for Unix getting this Very Wrong is that there is a whole CATEGORY of software that exists only to work around the problems it causes.
@jk Regardless of your stance, "documented consistency" is key.
While /etc holds config for all sorts of random stuff, everyone knows where to find the default config for, say, nginx or gimp.
"put all stuff for one program into one dir" has lead to the opposite. e.g. on my Linux, I still have no idea where firefox keeps its logs, history and config (it keeps everything in some nonstandard profile dir, is all I know).
So you still need a solid standard and adhering to that standard, regardless
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!