this post was submitted on 15 Aug 2025
721 points (98.3% liked)

Programmer Humor

25730 readers
1247 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
 
you are viewing a single comment's thread
view the rest of the comments
[–] NJSpradlin@lemmy.world 7 points 22 hours ago (14 children)

I find myself having too many nested folders, and I’m just a normie. I wonder how deep they go for you tech people.

At some points, Windows won’t let me change the file name because it was too long and I’m assuming the file path to it plus the ridiculously long name (“person last name, first name - type of document (purpose) yyyymmdd”) just breaks Windows.

Sometimes I have to copy those files to my desktop just to rename the new file, so that I can upload the file to an online system that only lets me upload files with names under 42 characters long. It’s wild.

[–] Eheran@lemmy.world 6 points 22 hours ago (6 children)

You can enable long names in Windows, essentially removing that restriction and giving you the power of all the sub folders up to something like 26'000 characters.

  1. Open the Registry Editor.
  2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
  3. Find the LongPathsEnabled DWORD value, double-click it, and set its value to 1
  4. Restart your computer
  5. Be free and happy
[–] bleistift2@sopuli.xyz 3 points 21 hours ago (3 children)

And I guess this isn’t the default for backwards compatibility with 1978’s tech?

[–] dan@upvote.au 3 points 21 hours ago* (last edited 21 hours ago) (1 children)

A lot of apps still use legacy Windows APIs that don't understand very long paths. Those APIs have been deprecated for maybe 15 years or more, but developers are lazy. Microsoft can't add support for long paths to the old APIs because they use a fixed buffer size (which means that only a certain amount of memory space is available for the path, and increasing it would break the apps that rely on that). They can't totally remove the old APIs because every app that uses them would break.

[–] bleistift2@sopuli.xyz 2 points 21 hours ago (1 children)

They can’t totally remove the old APIs because every app that uses them would break.

For every other company I would buy that argument. But for one that forces customers to throw away millions of computers which can’t run Win 11… no.

[–] Eheran@lemmy.world 1 points 7 hours ago

People having to buy new hardware for new software is and has been normal forever.

People losing access to their software because the OS changes how it deals with something did happen, but that is not something anyone wants.

load more comments (1 replies)
load more comments (3 replies)
load more comments (10 replies)