I disapprove of the "new" way (that is not so new, but it is the current trend) because it favors lock-in and general loss of control. But there are also some advantages such as being able to do versioning, syncing, collaborative work, searching and general database-like operations when your filesystem doesn't support it. A lot of popular open source "not evil" software use that model, for example, IIRC, Firefox has always stored bookmarks in an opaque sqlite database while Internet Explorer stored them as files in a folder, and I don't think I need to tell you which one is considered the most evil.
$ grep FIREFOX ~/.bashrc
export FIREFOX_DIR=$HOME/.mozilla/firefox/q3m93qpe.default-release/
$ cat ~/.local/bin/ff-tabs
#!/bin/bash
lz4jsoncat $FIREFOX_DIR/sessionstore-backups/recovery.jsonlz4 | jq -r '.windows[].tabs[].entries[-1] | .title, .url, ""'Some OS builders have been trying to push this model on the desktop but have not been very successful due to legacy. It only seems to be done with mobile apps running on the desktop (Windows with Android apps and macOS with iOS)
I also lament this model, I think we should always have full access to our devices. But there's a strong commercial push for lock-in and subscription models.
Non I've seen do a proper job of mounting as a drive, NFS or SMB would be nice.
The last MacOS update broke Spotlight indexing for my Google Drive folders. Really annoying not being able to use Spotlight (and by extension Alfred), so the only logical thing to do was move to iCloud.
In the process of moving off of Google Drive, I also decided to move my email to Fastmail and just ditch GSuite (or whatever they are calling it today) forever. I’ll sleep better at night knowing that Fastmail knows their place and (hopefully) won’t try and force a chat function into my web email client as a means to build engagement for a product I don’t care about.
However, there is a post on this site that has become infamous in which a commenter questions the need for Dropbox when stuff like SFTP already exists.
https://docs.microsoft.com/en-us/azure/storage/files/files-s...
I don't understand how SMB could work unless there was geographical replication to nodes closer to you, with some kind of load balancing to change the endpoint you're using to be closer to you.
https://docs.microsoft.com/en-us/windows-server/storage/file...
Tragically it was still trash.
WebDAV is kinda that. I subscribe to a (super cheap) hosted version from Hetzner and I'm happy with it even though the server is on a different continent. As mentioned somewhere in another comment, I also use rclone mount to use it, but there are other options as well (the client built into GNOME is reasonably good, the client built into Windows 10 is terrible).
I just tested with Slack, VSCode, and GIMP, and all three allowed me to browse and open from there.
I ended up buying InSync because it was 50% off in easter, and its Google Drive/Dropbox paths works perfectly even in the terminal. Unfortunately it lacks Google Drive streaming.
https://www.digitalocean.com/community/tutorials/object-stor...
Object storage isn’t random access (the ability to read and write any part of a file) the way a disk drive is. This causes complications for software that expects to be able to randomly access a file like they would on a disk.
Partial reads are supported everywhere out of box just by using the Content-Range HTTP header.
Partial writes aren't standard, but some implementations e.g. SabreDAV can do those using PATCH with X-Update-Range header (and e.g. rclone supports this).
WebDAV has its warts and limitations but it's a very underappreciated protocol.
> for which there exist multiple utilities to mount the thing as a local file system
Which all have their own sets of intricacies. The most obvious one being listing a directory is either impossible, costly, or as slow as the heat death of the universe. Other (far riskier) ones (from s3fs-fuse, which I have the most experience with[0] ) are the lack of guarantees about atomicity and concurrent access.