1416
top 50 comments
sorted by: hot top controversial new old
[-] disguy_ovahea@lemmy.world 292 points 3 weeks ago

This meme is way more clever than it should be

[-] runeko@programming.dev 64 points 3 weeks ago

Didn't realize until I read your comment. Thanks.

[-] Aurenkin@sh.itjust.works 44 points 3 weeks ago

I didn't realise until I read that comment, your comment and the other comment about slash direction.

[-] hemmes@lemmy.world 21 points 3 weeks ago

JFC, thank you. I didn’t realize until it was spelled out for me. I’m definitely not that kind of smart.

This is why I always sucked at games like Myst

load more comments (2 replies)
load more comments (2 replies)
[-] Rhaedas@fedia.io 35 points 3 weeks ago

It's not something the Jedi would tell you.

[-] Aurenkin@sh.itjust.works 41 points 3 weeks ago

Only a sith deals in absolute paths.

load more comments (1 replies)
load more comments (8 replies)
[-] nichtburningturtle@feddit.org 100 points 3 weeks ago

I hate that I need to use escape characters when creating something for windows.

[-] pennomi@lemmy.world 31 points 3 weeks ago

Python raw strings to the rescue!

[-] Diplomjodler3@lemmy.world 41 points 3 weeks ago

Pathlib is the answer.

[-] joyjoy@lemm.ee 17 points 3 weeks ago

Nobody is stopping you from using forward slashes. Python will translate the path for the current platform.

load more comments (1 replies)
[-] Diplomjodler3@lemmy.world 17 points 3 weeks ago

Try pathlib. All your problems solved.

[-] atx_aquarian@lemmy.world 74 points 3 weeks ago* (last edited 3 weeks ago)

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.

[-] Localhorst86@feddit.org 61 points 3 weeks ago

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.

[-] riodoro1@lemmy.world 30 points 3 weeks ago

Such a microsoft thing to do.

[-] The_Decryptor@aussie.zone 18 points 3 weeks ago* (last edited 3 weeks ago)

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.

[-] pixelscript@lemm.ee 16 points 3 weeks ago

For a few years now, Windows has had the capability of marking certain directories as case-sensitive. So you can have a mixed-case-sensitivity filesystem experience now. Yeah. :/

load more comments (1 replies)
[-] qjkxbmwvz@startrek.website 19 points 3 weeks ago* (last edited 3 weeks ago)

Although you can use case insensitive filesystems with Linux, and case sensitive filesystems with macOS. I believe the case sensitivity is a function of the specific filesystem


but yeah, practically, the root for Linux is always case sensitive, and APFS ~~ain't~~ is only if you ask it to be ( https://support.apple.com/lv-lv/guide/disk-utility/dsku19ed921c/mac ).

[-] paperplane@lemmy.world 16 points 3 weeks ago

When case insensitivity is the default I always wonder how many apps unknowingly rely on that due to typos somewhere. I encountered this once while porting a Windows/macOS app to Linux that someone imported a module with the wrong case and nobody noticed

load more comments (2 replies)
[-] frezik@midwest.social 15 points 3 weeks ago

I once ran into a bug in an Arduino program where it wouldn't compile. The author blamed my "broken environment". Turned out, he had included "arduino.h" instead of the correct "Arduino.h".

[-] ikidd@lemmy.world 11 points 3 weeks ago
load more comments (1 replies)
[-] MooseTheDog@lemmy.world 10 points 3 weeks ago

Least favorite part of linux honestly

[-] SaharaMaleikuhm@feddit.org 26 points 3 weeks ago

Case-insensitive filesystems are for maniacs. They are only causing trouble. Ever had two folders with the same name but different capitalization in windows? You see both, but whichever you click it will always open the same one, while the other can't be accessed. Psychopath behavior.

load more comments (5 replies)
[-] asdfasdfasdf@lemmy.world 13 points 3 weeks ago

Hard disagree. I don't understand why anyone would want case insensitive.

Am I the only one who doesn't go around mindlessly capitalizing letters? Do people find it too difficult to capitalize things?

Do you want case insensitive passwords too?

If I type X I mean X and only X. Uppercase letters are different letters, just like X and Y are different letters.

load more comments (3 replies)
[-] Trainguyrom@reddthat.com 12 points 3 weeks ago

Makes changing the case of a file/folder a lot easier though. Windows you have to rename it to something else then rename it again just to change case but Linux you can just...rename it. It's a small thing but it's something

load more comments (1 replies)
load more comments (3 replies)
load more comments (1 replies)
[-] pelya@lemmy.world 57 points 3 weeks ago

You can actually use / as a path separator on Windows in functions like fopen(), because it supports some ancient version of POSIX standard.

[-] palordrolap@fedia.io 33 points 3 weeks ago

There used to be an undocumented setting in early versions of MS-DOS that would allow the setting of the command option character to something other than the slash, and if you did that, the slash automatically became the path separator. All you needed was SWITCHAR=- in your CONFIG.SYS and DOS was suddenly very Unix-y.

It was taken out after a while because, with the feature being undocumented, too many people didn't know about it and bits of software - especially batch files, would have been reliant on things being "wrong". The modern support for regular slash in API calls probably doesn't use any of the old SWITCHAR code, but it is, in some way, the spiritual descendant of that secret feature.

Here's an old blog that talks about it: https://learn.microsoft.com/en-gb/archive/blogs/larryosterman/why-is-the-dos-path-character

[-] marcos@lemmy.world 13 points 3 weeks ago

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.

[-] friend_of_satan@lemmy.world 34 points 3 weeks ago* (last edited 3 weeks ago)

Also the internet belongs on the left.

And really, Linux/macos could be reduced to "Unix" https://upload.wikimedia.org/wikipedia/commons/7/77/Unix_history-simple.svg

[-] SatyrSack@feddit.org 25 points 3 weeks ago

And BSD. It's really just Windows vs. literally everything. Or is there anything else that uses backslashes?

[-] db2@lemmy.world 24 points 3 weeks ago

CP/M

Which in this context is named hilariously.

[-] shotgun_crab@lemmy.world 11 points 3 weeks ago

Typical windows behavior

load more comments (4 replies)
[-] MooseTheDog@lemmy.world 26 points 3 weeks ago

File systems aren't even real.

[-] BigDanishGuy@sh.itjust.works 11 points 3 weeks ago

What is this "real" concept anyway?

Adam Savage famously stated on Mythbusters "I reject your reality and substitute my own"

Sure, but is reality even real then? Is anything real?

Not that I meant to get all pop-philosophical on this beautiful Sunday morning, sorry about that.

load more comments (1 replies)
[-] umbraroze@lemmy.world 22 points 3 weeks ago

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

load more comments (1 replies)
[-] nexguy@lemmy.world 21 points 3 weeks ago

Would it be more efficient to say Unix vs Windows?

[-] wreel@lemmy.sdf.org 15 points 3 weeks ago
[-] Excrubulent@slrpnk.net 11 points 3 weeks ago

I'd just like to interject for a moment. What you're refering to as Linux, is in fact, GNU/Linux, or as I've recently taken to calling it, GNU plus Linux. Linux is not an operating system unto itself, but rather another free component of a fully functioning GNU system made useful by the GNU corelibs, shell utilities and vital system components comprising a full OS as defined by POSIX.

Many computer users run a modified version of the GNU system every day, without realizing it. Through a peculiar turn of events, the version of GNU which is widely used today is often called Linux, and many of its users are not aware that it is basically the GNU system, developed by the GNU Project.

There really is a Linux, and these people are using it, but it is just a part of the system they use. Linux is the kernel: the program in the system that allocates the machine's resources to the other programs that you run. The kernel is an essential part of an operating system, but useless by itself; it can only function in the context of a complete operating system. Linux is normally used in combination with the GNU operating system: the whole system is basically GNU with Linux added, or GNU/Linux. All the so-called Linux distributions are really distributions of GNU/Linux!

load more comments (2 replies)
load more comments (5 replies)
[-] brotundspiele@sh.itjust.works 12 points 3 weeks ago

You mean right vs. wrong?

[-] cupcakezealot 16 points 3 weeks ago

Why fight when you can just do cd /mnt/c/Program\ Files\ \(x86\)/

[-] glowing_hans@sopuli.xyz 15 points 3 weeks ago

Duel of the fates: \//\

[-] SendMePhotos@lemmy.world 11 points 3 weeks ago
[-] Diplomjodler3@lemmy.world 66 points 3 weeks ago

Linux uses forward slash. Windows uses backslash. Because some dude 45 years ago wanted to make it look different from UNIX.

[-] HakFoo@lemmy.sdf.org 16 points 3 weeks ago

I understand pre-OS X Macintoshes used colons.

[-] PNW_Doug@lemmy.world 20 points 3 weeks ago

They did! And I weirdly kind of miss them for the entirely non-logical reason that they looked elegant.

Don't get me wrong, I adapted in about 3 seconds when I made the switch to Mac OS X 25 years ago, but I irrationally kinda miss them just a tiny bit.

load more comments (1 replies)
load more comments (1 replies)
load more comments (5 replies)
load more comments (2 replies)
load more comments
view more: next ›
this post was submitted on 01 Feb 2025
1416 points (100.0% liked)

Programmer Humor

20778 readers
1495 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS