Spacedrive – A File Explorer from the Future

Hum, try to imaging a new files manager: instead of force you traversing a tree it gives you a search&narrow UI, not just in files names but in a sort of metadata-rich notes/headings witch may also have a file or more attached or may not. Imaging you hit a key and type things like:

- "ph b" and just phone bills results appear

- "car ins" and car(s) insurance(s) appears

- "ph sum" and some summer photos "notes" with location and year tags start to show

- $your_host_name and it's NixOS config is there

- "zsh" and the relevant commented zsh config arrive

- "foo bar" and foo bar contact note arrive, with links to mail search, projects up with him/her, few noted threads, some files, contact info, ...

Well... That's how I manage 99% of my digital stuff, Emacs/org-mode(notes)/org-roam(UI to access|manage them)/org-attach(to have files there without having to manually manage them in a hierarchy), for mail notmuch and ol-notmuch to link searches and threads/messages etc and so on.

Why? Because my brain is a chaotic graph, not a specialized tree so while some treeviews are nice sometimes I need many of them for the same contents, depending on the context, because sometimes I have to note small things, not enough to be in a single file, with a name, properly placed somewhere for easy retrieving. Also I have only one brain, no reason to partition things like: this is where I look for notes, this for docs, this for emails, this for contacts. Did you know Google Search? Well if a unique UI is good to look for anything why not having the same on my desktop, locally, for my info? Why having countless separate apps with only context switch (Windows Management) and cut/copy/paste for IPCs? Unix at it's time at least offer decent CLIs IPCs, older systems offer more in GUIs, Emacs is an old and modern one who offer such IPCs and more important a total integration. Why have a collection of scripts, so files, some shell functions (more than one per file), aliases etc if anything can be just elisp?

Well... That's the file management of the very past (Xerox workstations, LispM etc) AND for the present AND for the future. All modern apps try to achieve this goal a small step at a time, like this project with tags, some have already goes farther (see tabbles.net, tagspaces.org and so on) but all quickly hit their architectural limits of the OS/environments they run and even for achieve just a small part of the game their complexity is extreme.

Long story short: we are told that we need separation, an app a job, we start following that model and quickly any apps try to incorporate and duplicate functions of others, they are hyper hard to integrate each others etc => separation works to sell software as products and services and surroundings a need for some against the others. We need unique systems, an application is the entire operating system and all the rest, easy to be mold by it's user. Witch happen to be a user, not a human-robot able just to click around.

Sorry for being rude, but IMVHO it's about time rediscover such classic concepts instead of investing countless resources in new stuff with same limits of the new classic model...

The native Mac Finder app is very unresponsive and clunky and I don't think there's any JS involved.

huh... and here I am, always long-clicking the back button for the back button history.

Long left-clicking has the advantage of saving one click when you immediately drag your mouse down to the page you want to go back to.

Sure, yet apps like Spacedrive use sluggish React with shadow DOM

The actual problem I need solving: multiple copies of files in multiple places, older versions of documents not linked to to the latest versions, disorganized backups.

Also - as a potential user, I would much prefer to read about useful features, rather than what language it's written in and why. (Rust! Webviews!)