That's idiotic. We all know it's a file, everything's a FILE!
linuxmemes
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry of any kind will not be tolerated. This is an LGBTQ+-friendly community -- if that is a problem for you, you should leave.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
- Don't come looking for advice, this is not the right community.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves / tolerates / hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
Anyone gives me a hard time about that, Iβm reverting to Amiga and calling it a βdrawerβ
i just call 'em all "that fuckin' thing" and if anyone complains, they can talk to this guy

I use directory and folder interchangeably
Don't care, KDE says "create new folder", it's a folder.
I call them "bags of holding" because their capacity is undefined.
Call them inodes and see what happens next
An inode is not a folder it's metadata for a folder OR a file.
It would be more correct to say all folders are txt files
iNod
You'll pry my old outdated terminology from my cold dead hands lol
I'll toast to that from my Remix OS coffee mug currently sitting on my SunOS mouse pad.
ZFS head correcting you to "dataset"
Tbf Dolphin calls them folders
All hail our dolphin overloads
And every Linux directory icon is a folder. This is a non issue.
Shhhh the CLI purists haven't figured out what icons are yet.
Gooey? Sounds gross
You mean those religious pictures old Italian and Russian people have?
wait, are CLI purist the purest keyboard warriors?
Anyone who doesn't post their rants via curl is a poser
Indeed, any other is merely a "desktop metaphor warrior"
oh oh! Are those the extra logos and things added by nerdfonts?
What would the icon for a "directory" look like?
something very similar in mainframe land where they call files "datasets." if you call a dataset a file, get ready to get an earfull!
which is ironic considering IBM themselves often call them files and one of the most popular dataset utilities is called FileAid. but if we acknowledge that, we lose a valuable opportunity to belittle and exclude newcomers
In AWS S3, they're objects, not files. But you upload files to objects. And can download an object to a file. But they're not files. Trust me bro.
There is a reason for that since S3 is not block storage and doesn't have a Hierarchal filesystem. That's why when you create folder in the S3 console what you are really creating is a prefix meaning its just a placeholder to auto add the prefix string to the beginning of all objects. But all objects in the bucket are flat when it comes to the API. Plus the way the files are stored in the shards in S3. You can limit Throughput by treating prefixes like a hierarchical filesystem too much.
The more confusing thing I've had to explain to too many developers is that it's not a directory regardless of what it looks like on the AWS website view. It's a "prefix" meaning the entire thing, including the slashes, is just part of the filename, there is no real structure inside a bucket. So there's no such thing as relative paths to search for things. When you call the list objects function with a prefix it's the same as doing a "starts with" on a string. You can't give it a partial "path" relative to another object that appears to be in another "folder".
You know, the same deal kind of applies about "losing newcomers". Because I avooded using AWS because everything seemed cryptic and weird with its terminology. So other companies got my business.
Itβs called gatekeeping. You wouldnβt get it.
Reminds me of the oilfield unit hell. If you even mention an SI unit on an offshore drilling platform, your beheaded carcass will be displayed on top of the derrick as a warning for others, left to be devoured by birds and the salty wind.
Just call it a 'container object' and you can be technically correct in almost every context.
See also: in SQL and Dataverse, a row is called a 'record', but in SharePoint and Lists, a row is called an 'item', and MAN do people get all pissy if you get them mixed up or refer to it as a 'row'.
It's even more aggravating when you understand that 1) they're all different implementations of the 'table' data structure, so the term is still accurate; 'records' and 'items' are just subsets of 'rows', and 2) SharePoint and Lists are just SQL on the backend anyway.
Like, obviously you knew what I meant, but how is your ego gonna get stroked unless you preach about pedantic details that don't matter?