Tbf Dolphin calls them folders
post
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.
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.
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/dir2 with "directories" inside, each one with millions of "files"/objects. When you try to "ls" the dir1/dir2 by querying Prefix='dir1/dir2/' and Delimiter='/' 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 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".
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.
For what it's worth, they're referred to as directories by command prompt and PowerShell (effectively the new Windows command prompt) tools as Windows as well.
And always had been in DOS before Windows.
Folder is just an easier concept for the average person to grok, so I say folder to them.
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
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?
That's idiotic. We all know it's a file, everything's a FILE!
Anyone gives me a hard time about that, Iβm reverting to Amiga and calling it a βdrawerβ
You'll pry my old outdated terminology from my cold dead hands lol
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.
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.
When you accidentally say "deck" instead of "library" in your MTG group
Anyone else catch shit for saying machine or box?
"Yeah it's a Windows box so whatever is trying recon knows nothing and hasn't learned after repeated attempts."
"The Honeypot? Yeah just a Linux box that blows up our alerts channel if anyone tries to touch it."
Etc.
No. Why would they?
A box shaped computer? so pedestrian, mine is a hyperbolic paraboloid.
I've heard some techs complain that a 'machine' can be physical or virtual, but a 'box' always refers to a physical machine. I don't really agree with that distinction; if the difference matters, say "physical machine" or "virtual machine". In 99% of cases, whether a machine is physical or virtual is a distinction without a difference anyway.

top 73 comments