- cross-posted to:
- linuxmemes@lemmy.world
- programmerhumor@lemmy.ml
- cross-posted to:
- linuxmemes@lemmy.world
- programmerhumor@lemmy.ml
You must log in or register to comment.
This meme is way more clever than it should be
Can you please explain? I’ve never used Mac and it’s been a long time since I’ve properly used windows.
File paths in Linux and Mac use / while Windows uses \
Take a look at the angle of the lightsabers.
I never would’ve gotten that!
Like I said, way more clever than it should be. Props to the creator for sure.
Technically, Windows understands both / and \. I personally always use / just because it’s easier to type that.
The lightsaber orientation is the same as the slash orientation
Ha, neat!
Took me a minute
Didn’t realize until I read your comment. Thanks.
Why fight when you can just do
cd /mnt/c/Program\ Files\ \(x86\)/also applies to unix vs dos
I hate that I need to use escape characters when creating something for windows.
Python raw strings to the rescue!
Nobody is stopping you from using forward slashes. Python will translate the path for the current platform.
Python doesn’t have to. Windows supports both out of the box. Has been for many, many years
\o/
I don’t really watch Star Wars. I’m a more of a Trekkie gal.
🖖
See, you can separate files both ways as long as it’s logical
Duel of the fates:
\//\I don’t get it
The lightsaber direction is like / \
A whole fight in characters:
/ \
X
| |
\ /- /
X
- /
Ohhhhh… I fucking hate this. I use Windows locally, but I do support for a render farm that runs on Linux. The number of times I have recieved “it works locally” tickets from an artist who decided to get clever and embed Windows paths in string literals in their scene makes me want to punch a puppy. They don’t even look at the application logs we provide to see that the paths threw errors. We handle repointing their file paths with symlinks normally, but when they use literals it literally fucks the system with escapes. I will never understand why Microsoft refuses to standardize to POSIX with the rest of the world. Aside from them being a US company with decision makers who still think freedom units make sense.
You can actually use / as a path separator on Windows in functions like fopen(), because it supports some ancient version of POSIX standard.
The one thing about NT was that it didn’t have it’s own semantics, but it could emulate any system you wanted. It’s the unofficial successor of an OS that was based on creating VMs where you could run any other OS you want.
Then Microsoft decided to create their own system in it, and only really finished writing that one.
The big reveal comes when you realise the paths are in fact, relative.
Both works fine in Windows tho?
Used to not
Times change. You used to not be able to run Linux in Windows, but you can do that too.
Yeah, and I’ve tried that. It turns out it works even better if you throw away the Windows part.
Fun fact, though: Linux is the only case-sensitive one.
Edit: I feel silly for forgetting that it’s all about the choice of FS. If anyone needs anything from me, I’ll be in the corner, coloring.
From a technical standpoint, the windows NTFS filesystem is designed inherently case sensitive, just windows doesn’t allow creating case sensitive files.
Connecting an NTFS drive to linux, you can create two separate files readme.txt and Readme.txt.
Using windows, you can see both files in the filesystem, but chances are most (if not all) software will struggle accessing both files, opening readme.txt might instead open Readme.txt or vice versa.
Such a microsoft thing to do.
NTFS was designed back in the mid 90s, when the plan was to have the single NT kernel with different subsystems on top of it, some of those layers (i.e. POSIX) needed case sensitivity while others (Win32 and OS/2) didn’t.
It only looks odd because the sole remaining subsystem in use (Win32) barely makes use of any of the kernel features, like they’re only just now enabling long file paths.
