> so you can sort, tag, backup and share files without limitations of any one cloud provider
I don't have a "cloud provider".
I guess I'm not from the future. ¯\_(ツ)_/¯
Spacedrive – A File Explorer from the Future
41–50 of 72 posts
Re: Spacedrive – A File Explorer from the Future
#42Earlier quoted context omitted.
VSCode devs do some magic trickery to improve Electron's performance, but it is by design not in the league of Neovim or even fully fledged Qt Creator in terms of responsiveness.
Considering the popularity of VS Code over NeoVim and Qt Creator, I guess it's responsiveness is good enough for the vast majority
Whatsapp is good enough for the vast majority too. Doesn't mean that I'll subject myself to it.
Re: Spacedrive – A File Explorer from the Future
#43The 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!)
It looks like a good, useful idea but you should explain to your user what it does. Perhaps show some screen-shot animations?
Re: Spacedrive – A File Explorer from the Future
#44If your designer suggests grey text on a black background, fire them.
Parts are completely unreadable, other parts only hard. Not worth the bother.
Re: Spacedrive – A File Explorer from the Future
#45If your designer suggests grey text on a black background, fire them. Parts are completely unreadable, other parts only hard. Not worth the bother.
Of course it's bad for accessibility, but for me only the "Coming soon..." text on the start page is hard to read. Maybe you have your screen set too dark? Anyway, it feels a bit harsh to discount the whole project because of an unfortunate design choice...
Re: Spacedrive – A File Explorer from the Future
#46I tried something similar with a project of mine[1], with a focus on API rather than frontend so I could build tailored apps for each device/user. At some point I should get around to finishing it -- I mostly focused on S3 and local filesystem compatibility, but being able to explore filesystems from other devices (maybe through an agent) is a neat idea.
Re: Spacedrive – A File Explorer from the Future
#47Earlier quoted context omitted.
VSCode devs do some magic trickery to improve Electron's performance, but it is by design not in the league of Neovim or even fully fledged Qt Creator in terms of responsiveness.
Considering the popularity of VS Code over NeoVim and Qt Creator, I guess it's responsiveness is good enough for the vast majority
I use all these editors, and I'd say that for purely editining purposes Neovim feels incredibly responsive, it's something that requires the whole UI framework to be fast. What keeps me from switching from VSCode are its great plugins
Re: Spacedrive – A File Explorer from the Future
#48Earlier quoted context omitted.
Interface responsiveness matters
The native Mac Finder app is very unresponsive and clunky and I don't think there's any JS involved.
Well, it may scan the file system, which takes a heck of a long time, even on an NVMe drive. Or they broke the fuzzy finder/caching mechanism
Re: Spacedrive – A File Explorer from the Future
#49The site breaks the back button in Firefox.
Chrome on Linux too
Re: Spacedrive – A File Explorer from the Future
#50Earlier quoted context omitted.
VSCode devs do some magic trickery to improve Electron's performance, but it is by design not in the league of Neovim or even fully fledged Qt Creator in terms of responsiveness.
Considering the popularity of VS Code over NeoVim and Qt Creator, I guess it's responsiveness is good enough for the vast majority
It is popular yes. But with NeoVim I feel so damn productive. VS Code feels sluggish compared to NeoVim. At least for me.