• SCmSTR@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    10
    ·
    edit-2
    1 day ago

    Yeah but then I can’t tell what filetypes they are. Having the type directly in the name is an awesome convention. And theoretically, it prevents the os from having to read every file’s contents. And it’s good for not having to use thumbnails. So you can have more condensed file browsing. It’s also better for proprietary filetypes and new things since the os doesn’t need to know wtf something is.

    Your logic reminds me of using nondescript variable names in programming. Yes, the system will probably know, but I’m the user, I’m the person this is all for. And it’s good convention to have good naming convention. File extensions are nice to have and good convention.

    • Amon@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      23 hours ago

      fair enough but i have the unpopular opinion that file extensions should be a prefix not a suffix so that all files of the same type sort together

      • SCmSTR@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        1
        ·
        22 hours ago

        Mmmm… As long as the os treated it as separate from the filename. One of the reasons extensions exist is so that the name of the file doesn’t encroach with the self-identifying-filetype/extension. If you put it at the front as a prefix, you would lose the ability to have EITHER names of files OR extensions as separatable and simultaneous ordering systems.