Funny thing is Windows accepts forward slashes as arguments in programs and API for long time. They just refuse to return forward slashes and don't give users/developer options to do so, so we have to deal with it anyway
I think you mean users\developers
DIR 🤪
On Windows 11 it's possible to use backslash for path in the terminal. But then it's windows 11 and their million bugs
Windows just wants to help you learn about escape characters
\
CR LF
I hope the file encodings CEO and the line endings CEO trip over something and break their nose
Also whoever decided to do strings in WTF-16
Ahhhh I get it
Yeah, I only got it after I bumped into it second time
Now do a loss crossover.
I I ı
I I I _
::|:;
you lose a hand specifying linux file paths?
If you use the character 0x20 in a file name, yes
No! That’s impossible!
It’s the Overly-VerboseCommandSyntax in PowerShell that always grinds my gears.
Old Mac OS before Mac OS X used
:as path separatorMacintosh HD:Users:yourUserName:Desktop:My File.txt. It’s still used for AppleScript. Converting from and to POSIX paths using/happens pretty regularly when writing AppleScript nowadays.That’s also the reason why
:is still an illegal character to use for file names on macOS.All too easy
I've never met anyone who likes the windows shell environment, or uses it by choice. Only people who try very hard to convince themselves UNIX is somehow worse.
