• 2 Posts
  • 57 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle
  • QuazarOmega@lemmy.worldtolinuxmemes@lemmy.worldNaming Torrents
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    1 year ago

    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


  • QuazarOmega@lemmy.worldtolinuxmemes@lemmy.worldNaming Torrents
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    1 year ago

    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’ve been loving it honestly, I used to mess up my systems pretty often in a way that upgrading to new releases had to be done from the command line because of random repositories I added, so things felt unstable.
    Immutable systems on the other hand are dumbass (me) proof and I can still do what I used to do with those repos in safe environments or Flatpak now that it has become so ubiquitous for packaging.
    Immutability is not a must, even though I really like the philosophy, in fact, if you’re comfortable with what you have, you might be fine just converting over your current OS to btrfs.

    Good luck, whichever option you try!