4 ms·
I'm not going back to CamelCase or underscores for my normal day to day file naming. The problem with spaces only exists inside the IT world and it's something
by HeadsUpHigh 6y ago
I'm not going back to CamelCase or underscores for my normal day to day file naming. The problem with spaces only exists inside the IT world and it's something they should find a way around.
- enriquto 6y agoI agree. The file load/save dialogs of all GUI should work in such a way that spaces typed by the users in a filename field are always transparently changed to something different (for example, the unicode non-breaking space).
- skissane 6y ago> (for example, the unicode non-breaking space) That's potentially even worse in a file name than plain old space is. It looks like a normal space, but isn't. If you are going to replace spaces in file names with something else, underscores are the best option I think.
- HeadsUpHigh 6y agoSounds like taking the "I know better than the users to another level".
- jyounker 6y agoAt the point I'd be happy if all unix tools had a `--json` option. Then the whole space issue goes away. So do a bunch of parsing issues. Unix tools standardized a character representation (e.g. everything is ascii). The next step is a unified standard the syntactical representation.
- laumars 6y agoASCII isn’t just a “character representation” though. It includes code points for data serialisation and transmission control. You can represent tables in ASCII without resorting to printable characters nor white space as field separators. I don’t why POSIX tools don’t already do this but I suspect it’s because most tools would have evolved by accident rather than being designed from the ground up with edge cases in mind.