• _NetNomad@fedia.io
    link
    fedilink
    arrow-up
    91
    ·
    29 days ago

    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

    • bobzrkr@sh.itjust.works
      link
      fedilink
      arrow-up
      56
      ·
      29 days ago

      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.

      • ViatorOmnium@piefed.social
        link
        fedilink
        English
        arrow-up
        8
        ·
        29 days ago

        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.

          • ViatorOmnium@piefed.social
            link
            fedilink
            English
            arrow-up
            3
            ·
            28 days ago

            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.

              • ViatorOmnium@piefed.social
                link
                fedilink
                English
                arrow-up
                1
                ·
                26 days ago

                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.

      • agentTeiko@piefed.social
        link
        fedilink
        English
        arrow-up
        5
        ·
        28 days ago

        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.

    • Err(()).unwrap()@lemmy.worldM
      link
      fedilink
      arrow-up
      10
      ·
      edit-2
      29 days ago

      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.

  • wizardbeard@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    33
    ·
    29 days ago

    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.

    • Onomatopoeia@lemmy.cafe
      link
      fedilink
      English
      arrow-up
      29
      arrow-down
      2
      ·
      29 days ago

      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.

  • Dookieman12@piefed.social
    link
    fedilink
    English
    arrow-up
    26
    ·
    29 days ago

    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?

  • bigbangdangler@reddthat.com
    link
    fedilink
    arrow-up
    6
    ·
    28 days ago

    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.

  • foggy@lemmy.world
    link
    fedilink
    arrow-up
    8
    arrow-down
    4
    ·
    29 days ago

    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.

    • Dookieman12@piefed.social
      link
      fedilink
      English
      arrow-up
      4
      ·
      29 days ago

      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.