It is good that these "water is wet" statements get written down so we can point humidity-skeptical people to them from time to time. The deeper problem is the sad state of affairs of distributed computing for the end user : * Application instances expect to be the only ones modifying the files that underlie the document being edited. Most of them simply bail out when the files get modified by another application. *…
> We need local desktops with a decent distributed filesystem, and vendor agnostic access to that filesystem from all our devices. I am very happy with pCloud. One of the reasons I got it is: it works very well on Linux. It works on Android. It works on Windows. And it works in the browser, for things like video and photos. Also: no risk of trigger-happy account deletion like with Google, if pCloud dies my email stil…
So a vendor has the power to disrupt you whenever they feel like EOLing the service you depend on. I understand that's as good as it gets today, but it's not good enough.
For me, the only acceptable level of impact is as follows:
* vendor X sunsets their service by date D
* before date D, I sign-up for a new account with vendor Z and configure it in my filesystem settings
* I set vendor X as "deprecated,EOL-date=D" in my filesystem settings.
Then my filesystem takes care of everything else for me transparently, with zero downtime and zero effort. Date D comes and goes and I haven't noticed a thing.