3 ms·
Yeah the big mistake was thinking spaces in file names was a good idea. It's not it's a terrible awful idea. Course not have a hard separation between paths an
by Gibbon1 3y ago
Yeah the big mistake was thinking spaces in file names was a good idea. It's not it's a terrible awful idea.
Course not have a hard separation between paths and file names is also not good.
./folder_what/folder_x/folder_zee:file_name.whatever
The above would be better
- SAI_Peregrinus 3y agoHow would it be better? Lots of names for people & things include spaces, so file names related to those people or things naturally would also include spaces. John Smith's name is John Smith, not John_Smith or JohnSmith or johnsmith or any other mangling.
- Gibbon1 3y agoYeah and still you shouldn't break your encoding in such a gross way just because of that. Also please for the love of god do not use peoples names as file names because they are not unique and they change oftener than you think.
- Clamchop 3y agoNot every usage of files is going to be at a scale where we have to worry about collisions, and anyway it's tangential. Whatever the concern, the ship has long since sailed on spaces in filenames, it's not going to be undone, and we are obligated to handle them.
- xmcqdpt2 3y agoI mean, I don't see why I should work around legacy limitations of 1970s software today, whenever I use a computer. Otherwise we might as well decide that file names should have no capitalization and be eight characters long, or that paths should be limited to 127 characters, etc.