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
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!).
I think you’re misremembering a little. Long filenames was introduced in Win95.
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.
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!
I still use spaces
agreed, “still worth it”
I do, however, tend to keep spaces out of my folder names so i can just use quotes at the end.
/Images/Halloween/Projections/“Creepy Crawlies.mp4”
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
Can’t relate. I use shell all the time, and I always use spaces in file paths, especially to make sure scripts I make still work then
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.
Given even what little I know of their history and what they are doing now, I cannot be sure this wasn’t the intention at least partially
No this is just clever
what is even more funny about this is that the name of that directory used to be locale-dependent, so in sweden it was just called “Program”, completely nullifying that idea.
It’s only localised in the file explorer. The actual folder name is always Program Files.
Only since vista, it used to be localized.
Really? That is absolute insanity
what about placeholders/variables like %localappdata%, %windir%, %programfiles%?
I can only assume these always existed, otherwise it would have been a nightmare for everyone.
Excel used to have, and I think it still has, localised function names.
Makes it a nightmare to look up stuff on the Internet.
the entirety of office has localised hotkeys. whaddayamean ^F is “search”? it’s for fat text!
C:\Program Files
C:\Program Files (x86)
C:\ProgramData
C:\PROGRA~1
The fucking parenthetical x86 absolutely kills me. I don’t normally wish dick cancer on people,
I’m a big fan of PascalCase. ThisIsAGreatFilename.odt
Rust made me have an habit of using snake_case… .rs
Mv /home/“$USER”/Downloads /home/“$USER”/downloads
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)
I tried to pause the first one but got all confused because there’s no closing single quote.
“inverted commas”? single quotes?
Yes, I am a weird english.
What is the Old Continent name of those: `
On its own, the backtick is primarily used in computing, and so doesn’t have an old-timey-English name, nor does the Jargon File mention a Commonwealth Hackish name for it. While there are a variety of other names, I don’t think any of them are specific to the UK
When used with a letter, it marks a grave accent; this was its original purpose on a typewriter
Floating commas
In dutch I’ve heard them be called flying commas unapologetically (vliegende comma’s — ironically has one in it because many plurals need it, it doesn’t mark possession)
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]/ +page.ts [[community]]/ ±page.ts posts/ [...postIds@]/ +page.ts
sveltekit is beautiful (thanks for spreading the word)
Im trying it out yet. It seems fun, the tutorial is amazing. I don’t think I’d want to do large enterprise projects with it
Have you noticed issues that you think would arrise at scale, etc for an enterprise project?
I’m using it for a small/medium sized project and it’s great and has not got in the way once. Wondering how you feel, since I don’t have experience with much enterprise code.
Oh. No. You win. Mine is a gut feeling that modeling all routes with folders would become a paid. To navigate and manage, while you have actual experience
" is your friend
Yep, exactly. And tab. \<space> is weird at first but makes sense if you think about it
i y’all just started using fish shell, you’d have proper shell completions and argument splitting that doesn’t care about spaces in file names
Are you typing the whole filename by hand? Tab expansion exists, you know?
If it fucking works…
Sometimes it does. But not always.
Zsh changed my life, but I still hate escape chars in my command lines for readability reasons
deleted by creator
“_” to the rescue
Now I use lowercase and underscores everywhere.
Hyphens > underscores for filenames because all web standards prefer hyphens so if you ever want to network your files its a much smoother experience!
This is what I need, an explicit reason that makes one choice better than another. If hyphens make for a smoother experience, then I’ll reconsider my default behavior.
Thanks for pointing out this benefit.
They suck hard. I use the renpy engine and there you reference file names directly but always lower case and spaces and hyphens turn to underscores. That can cause issues, so I just do underscores in my file names. Don’t give damn about the web.
I prefer lowercase with hyphens, but I’m transitioning into a team that does everything camelCase, which is the second best case, but I still strongly dislike it.
This is the best for tab completion, altho I prefer hyphens visually