Spacedrive – A File Explorer from the Future
spacedrive.app
spacedrive.app
I definitely see it as a feature, but I don't choose software solely based on this.
It's also likely that if you're using rust you care about performance and have thought about it while building your application, this is also a feature.
What's fascinating to me is everyone who says written in Rust isn't a feature. It definitely is, and it's going to keep eating C and C++'s lunch in new areas every year.
You seem to have a lot of expectations & be uninterested in the underlying technology. Open source is about more than "things work as advertised;" it's also about picking good tech & insuring we have open paths to the future we can advance on.
Your belief that "Needs to be a lot further along," applies to who? Yourself? Everyone? This seems like a great pitch to me, at a great time to get onboard.
https://github.com/spacedriveapp/spacedrive#developer-instal...
Not clear on what the build gets us from the roadmap
https://github.com/spacedriveapp/spacedrive/blob/main/docs/p...
As one of the core team has mentioned, they didn't post it themselves, but rather a community member posted it.
It's definitely something that I'll be bookmarking for later though. It's a tool I could see myself using.
Those features are from the future ;-)
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!)
My friend, an engineer for a Fortune 500 was lamenting to me recently having had someone overwritten one of his designs on a shared drive. He had to get IT to pull a backup.
It absolutely perplexes me that DVCS isn't the norm outside of programming.
There's irmin[1][2], a git-like database written in Ocaml. I was always confused by how git-like it was... at points I thought there was outright interoperation. But I'm not sure what if any software was ever written on irmin.
I have my own project pr0x that has a file-persistence engine, which I need to spend a weekend adding git support to sometime. Very high importance to me, but haven't made it a priority.
Again,
> It absolutely perplexes me that DVCS isn't the norm outside of programming.
Absolutely perplexes me that programming hasn't made DVCS the norm in the outside world. We're steering this ship. People don't even have to know what's going on... we should still be using the best class tools on this planet to be managing data, and what data do we better manage/is more important to us than source code? It's up to us to seize this initiative.
[1] http://web.archive.org/web/20140719043152/http://openmirage.... https://news.ycombinator.com/item?id=8053687 (146 points, 8 years ago, 25 comments)
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.
We really need to unbreak the present before unlocking the future, or the future will still be broken.
Please don't complain about tangential annoyances—things like article or website formats, name collisions, or back-button breakage. They're too common to be interesting.
There needs to be a guideline about <please don’t link to the guidelines whenever someone does something helpful>
Not seeing anything about data protection.
Hammer2's wikipedia article lists dragonfly bsd as it's solely supported os and ceph requires one to... Manage a ceph cluster.
Now the question of whether this is similar to those technologies becomes easy to answer: no, they aren't similar. This tool aggregates external storage providers while the tools you reference require you to be your own provider.
My personal recommendation (if this project interests you) is to check out initiatives like upspin.io and Tahoe lafs
I don't have a "cloud provider".
I guess I'm not from the future. ¯\_(ツ)_/¯
Parts are completely unreadable, other parts only hard. Not worth the bother.
I was reading in the dark, so had brightness was low, but fine for any normal site.
This mistake is a common thing for people to complain about on accessibility forums. If you've lost lost any visual acuity, which a large percentage of the population has, your website is not usable.
- "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...
looking across lots of different storage locations can be deeply frustrating.
Last thing I want is a sluggish file manager that uses a crap tone of memory with a bunch of “ui renderer processes”.
Check out Pathfinder for a power user file manager done right.