• LalSalaamComrade@lemmy.ml
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        11 months ago

        Lately, I’ve started to hate scripted languages. That’s all I’ve got to say. You know, overhead and stuff? And well, much of it is just projection about how I can’t land even internships, because I decided to flunk on Golang and Rust. Ruby and Python ruined my early-career.

  • SmokeInFog@midwest.social
    link
    fedilink
    English
    arrow-up
    0
    ·
    11 months ago

    I don’t see how the tag => file path will be workable. As you add and remove tags, your actual file system is going to go strait to hell. Dear god I don’t want to think about what that would be like to browse from the terminal

  • taladar@sh.itjust.works
    link
    fedilink
    arrow-up
    0
    ·
    11 months ago

    That kind of storage might somewhat work for media files and simple tags if you only view the files in the tag-aware file manager but what about other applications and files?

    If the path of a file changes every time you add a tag or remove one that means the path of files is very unstable so you can’t e.g. reopen the last used files in other applications easily. I also don’t think this scales to the billions of files on a modern system. And of course any files required by an application to be in a specific place will be screwed up completely by this.

    Maybe the tag directories should be hard links to the actual files instead?

  • MonkCanatella@sh.itjust.works
    link
    fedilink
    arrow-up
    0
    ·
    11 months ago

    I’ve thought a lot about stuff like this and this is pretty cool but this basically looks like just a tagging system for files, which already exists in many ways. A true graph based file system wouldn’t just be an overlay over a directory tree. Would love to see some kinda filesystem dedicated to graph representation, where each file is a node with multiple edges.