Well yes, we use double quotes as you said, it may be annoying, but not difficult, sanitization is another matter.
I actually don’t remember of any terminal application that has issues with that, that’s why I made the original question
Edit: I understood now why you mentioned sanitization, double quotes shouldn’t be an issue because in filenames they are forbidden by the OS usually, that’s on the user if they try
Unpopular opinion maybe, but that’s just called bad programming.
For strictly code we can’t use spaces obviously, user input, on the other hand, should be handled gracefully always, not doing so is like those platforms that only supported ASCII even after the international userbase was already very prominent because the devs were just too lazy to update their systems to use Unicode (Windows is still like that with Powershell I discovered recently… shudders)
I don’t disagree, though I think they’re just a very minor annoyance that is easily adjusted with double quotes and tab autocompletion.
Personally I prefer to use spaces for many user facing files, like documents and images/media
Curious, where was the dot as separator for torrents born? Some kind of software limitation?
If that’s your only gripe with it, you can still access them by using one of the simple web servers available running inside Termux, that will also allow you to avoid CORS related problems, in fact it is the currently suggested method on MDN
Username checks out
Oh that’s interesting, I didn’t consider that, by the way is the brain really capable of reproducing life-like experiences or do we just fool ourselves into believing that our dreams were somehow more organic than they truly are?
Genuine question, why not?
Yes, that does sound reasonable