- cross-posted to:
- programmer_humor@programming.dev
- programmerhumor@lemmy.ml
- cross-posted to:
- programmer_humor@programming.dev
- programmerhumor@lemmy.ml
cross-posted from: https://lemmy.world/post/25005978
You must log in or # to comment.
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
Now do a loss crossover.
I I ı
I I I _
::|:;
Ahhhh I get it
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
wtf
It’s the Overly-VerboseCommandSyntax in PowerShell that always grinds my gears.
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.
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.
