Microsoft intentionally made programs install to C:\Program Files on Windows 95+ to force programmers to deal with spaces in filenames.

Someone make one of those "statements made by the utterly deranged" memes about it, please and thank you.

I've recently learned that in Linux, you can use emois in filenames. I died a little lot inside when I learned that.

I\ don\'t\ know\ what\ you\ mean,\ I\'ve\ never\ encountered\ any\ annoyances.

Oh\ come\ on,\ it\'s\ not\ that\ bad

Some shells enclose those types of files within inverted commas. Such that:

> ls
file\ name.md

is instead

> ls
'file name.md'

(I use fish)

Are you typing the whole filename by hand? Tab expansion exists, you know?

Now I use lowercase and underscores everywhere.

not sure why the default behavior is this:

file\ name\ with\ a\ bunch\ of\ spaces

instead of this:

"file name with a bunch of spaces"

but you can just press " before pressing tab to auto-complete, and it will use the 2nd form

the struggle between spaces in filenames look cute and oh fuck what's the code to reference a space in a filename in terminal?

I very intentionally have all my code in Personal Projects 🥰 and Work Projects 🏦 directories so I can find bugs in the handling of file paths.

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

" is your friend

Windows is stupid as shit, trying to shift+right click > open Powershell in a path containing a space results in it throwing an error, and you have to paste the path in yourself anyway

If your code is written well, it shouldn’t matter.

I'm a big fan of PascalCase. ThisIsAGreatFilename.odt

Don't try svelte kit. This is pseudocode but it's valid. The only symbol show here that is not real is the / that I've placed at the end of folder to show that they are folders. There are other special cases

routes/
+page.ts
(admin)/
  +page.ts
  [user=uuid]/
    [[community]]/
      +page.ts
    posts/
      [...postIds@]/
        +page.ts

Now I'm imagining a shell that looks iteratively through arguments to find where quotes would make total sense

$ ls
my victims.ods
$ wipe -f my victims.ods --thorough

So the shell would go like

1. wipe → command name found, ok
2. -f → no file in the current directory starts with that, skip
3. my → matches a file, keep in memory...
4. my victims.ods → full match, but missing quotes!
5. Prompt user:

Filename "my victims.ods" found without quotes. Choose:
[a]dd quotes this time
[A]lways add quotes (dangerous)
[n]o quotes today please
[N]ever offer adding quotes again
[t]ell me what could possibly go wrong when I choose to always add quotes
[P]unch the person who proposed this feature

smells like skill issue tbh

tools which cant handle being installed/run on directories with spaces are so annoying