• AmazingAwesomator@lemmy.world
    link
    fedilink
    arrow-up
    12
    arrow-down
    1
    ·
    edit-2
    3 hours ago

    i think i am old. i grew up using DOS, and really hated spaces in filenames and folders because they appreared truncated at the first space with a tilde and index of that file/folder representation.

    ex: C:\folder name is bad\ == C:\folder~1

    i hated that so much that when i got to windows 3.1 i refrained from using spaces (some command line was still necessary in w3.1)

    i have jept that habit through the years, so when i moved from windoes to linux, my natural instincts of snake_case_folder_names made it so i didnt have to change : D

    • wizardbeard@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      2
      ·
      38 minutes ago

      One of the fun things about modern Windows is that ~1 shit still appears every once in a rare while. Gotta love just stacking more and more shit on top of ancient systems in the name of backwards compatibility!

    • Onomatopoeia@lemmy.cafe
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      1 hour ago

      Yea, Win 3.1 didn’t support long names - that came with Win95. Win 3.1 was a shell on DOS.

      But I understand - it all blends together after um… 40 years (ouch!).

    • aaaaaaaaargh@feddit.org
      link
      fedilink
      arrow-up
      5
      ·
      2 hours ago

      That’s not even DOS I think. As far as I know Win 95 came up with this monstrosity in an attempt to circumvent the 8.3 character limitations present in older versions of DOS.

    • db2@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      3 hours ago

      I think you’re misremembering a little. Long filenames was introduced in Win95.