It’s the Overly-VerboseCommandSyntax in PowerShell that always grinds my gears.
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
On Windows 11 it's possible to use backslash for path in the terminal. But then it's windows 11 and their million bugs
I think you mean users\developers
DIR 🤪
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.
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
you lose a hand specifying linux file paths?
If you use the character 0x20 in a file name, yes
No! That’s impossible!
Now do a loss crossover.
I I ı
I I I _
::|:;
All too easy
