I can't remember it, but I read one Microsoft blog post (in Vista era?) about how one team at Microsoft would develop some amazing new Windows component. They'd proudly name it AmazingNewService.dll. And then the operating system team would come in and say "that's all fine and good, but you have to conform to the naming convention." 8+3 filenames. First two letters probably "MS", because of reasons. ...and 15 years later, people still regularly go "What the fuck is MSAMNSVC.DLL?"

[–] JasonDJ@lemmy.zip 4 points 2 months ago (1 children)

Why are they still so hung up on 8.3 long after Win95?

I get not wanting to have spaces in a filename. Those suck.

Is there something low-level that still doesn't like long filenames?

[–] umbraroze@lemmy.world 4 points 2 months ago

Well this was Vista era, they were probably doing that to ensure some sort of expectation from particularly tricky legacy apps. Windows prefers not to break old apps if at all possible.

[–] jjjasper@programming.dev 2 points 2 months ago (1 children)

sounds interesting~, any chance that I can find this post?

[–] umbraroze@lemmy.world 3 points 2 months ago (1 children)

Like I said this was in the Vista era. Or possibly before the Vista release, part of the Longhorn hype train (Longhorn got some super hyped features, such as an epic next-generation filesystem to replace NTFS, which Microsoft ultimately canned, and Vista ended up, you know, being Vista).

This was so long ago that I unfortunately don't remember what exact feature this was about, but it was about some new Windows component.

[–] jjjasper@programming.dev 1 points 2 months ago

Thanks anyway, first time know the 8+3 filename thing in MS