I say “directory” because I learned how to computer on MS-DOS.
If I’m browsing in a GUI they’re folders. If I’m using a CLI they’re directories. Except when I decide to do the opposite in either situation. Everything I do is the correct method and the only people who are wrong are whoever disagree with me. Unless they’re hot.
My OCPD:
Orange City Police Department
True…
Only the 1337 know that they’re really called “stores”. That’s why the command ls exists: list stores.
Obviously I’m kidding. It’s short for list, somehow. Just remove that unnecessary IT.
Ah the good ol’ “let’s abbreviate O_CREATE into O_CREAT”
or unmount into umount…
Go on, make your website colour=gray. Or was it color=grey?
No, ls is an abbreviation of look shit (up)
it doesn’t matter, we can live with just ls
That’s idiotic. We all know it’s a file, everything’s a FILE!
Would that make linux users filephiles?
Filephilefiles
Tbf Dolphin calls them folders
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.
You mean those religious pictures old Italian and Russian people have?
Was not expecting to see Padre Pio here. He was an oddly big deal in my elementary and middle school years.
Gooey? Sounds gross
yeah i much prefer see L eyes
oh oh! Are those the extra logos and things added by nerdfonts?
wait, are CLI purist the purest keyboard warriors?
Anyone who doesn’t post their rants via
curlis a poserIndeed, any other is merely a “desktop metaphor warrior”
What would the icon for a “directory” look like?
A phone book
According to Wikipedia, it is screenshot of MS Command Prompt 😂
Like a folder
All hail our dolphin overloads
What does Tuna call them?
Cans
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”.
That’s mostly because it doesn’t have real directories, it just simulates them with string prefixes and if you forget that on large buckets you are going to have a bad time.
What makes that different from a “real directory”?
Imagine you have
dir1/dir2with “directories” inside, each one with millions of “files”/objects. When you try to “ls” thedir1/dir2by queryingPrefix='dir1/dir2/'andDelimiter='/'S3 will still scan all the millions of objects starting with the prefix, and then filter out the ones that have a/after the prefix.And the benefit of this is …
There’s no benefit or drawback on it’s own. The way the keys and queries work are geared to S3’s nature as a key value object store - which requires it to support keys that wouldn’t be valid file paths or that have different delimiters.
In Magpiper, they’re Blarts.
deleted by creator
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.
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
When you accidentally say “deck” instead of “library” in your MTG group
When you accidentally call a hero a “champion” in your dota group
I use directory and folder interchangeably
Don’t care, KDE says “create new folder”, it’s a folder.
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
An inode is not a folder it’s metadata for a folder OR a file.
Demonstrating the parent’s point in real time.
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.
I got binders full of .txt files.
File and Folder are quicker to type. So I type that.
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?