this post was submitted on 23 Sep 2025
372 points (95.1% liked)

Programmer Humor

27214 readers
992 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
 

Re-posted to fix my filename emoji. You can't make this shit up

you are viewing a single comment's thread
view the rest of the comments
[–] NeatNit@discuss.tchncs.de 106 points 1 month ago* (last edited 1 month ago) (19 children)

You complain about ASCII filenames but a few of the examples are obviously Unicode, namely using emoji, well outside of the ASCII character set. But since you've brought up Unicode file names, let me introduce you to bidirectional text!

If you use Hebrew or Arabic, some of your directories or files will have right-to-left text in them. This is a recipe for disaster.

If in English you'd have "C:\Users\Adam\Documents\Research\Paper.pdf", which breaks down to:

  1. C:\
  2. Users\
  3. Adam\
  4. Documents\
  5. Research\
  6. Paper.pdf

In Hebrew you'd have: "C:\משתמשים\אדם\מסמכים\מחקר\מאמר.pdf", which breaks down to:

  1. C:\
  2. משתמשים\
  3. אדם\
  4. מסמכים\
  5. מחקר\
  6. מאמר.pdf

The entire path goes backwards, and the ".pdf" extension is visually attached to the "Users" folder if the text is rendered naively. It's insane. Fortunately many GUI shells nowadays separate each path item so they can't get intermixed like this. Example:

But still, if you copy a path into plaintext, it will still visually look wrong, and there is literally nothing that anyone can do about it. This is the correct way to render this text.

Exact same issues occur in Arabic and the few other RTL languages usedin the world. It's a massive pain.

Edit: oh, and on commandline on Windows, the required characters aren't even available by default so you get this lovely thing

[–] kopasz7@sh.itjust.works 2 points 1 month ago* (last edited 1 month ago)

Make it vertical? ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯

load more comments (18 replies)