3 ms·
The meaning of "desktop" has become moot. I suppose when I had an X-terminal and everything was "remote" it was fine. Before then I'd had diskless Suns and agai
by ggm 3y ago
The meaning of "desktop" has become moot. I suppose when I had an X-terminal and everything was "remote" it was fine. Before then I'd had diskless Suns and again, it was an NFS locally cached view into what was remote. So.. if we're returning to some sense that based on our priors (google cloud, onenote, dropbox) we believe a local cache is fine for faster access to something which is remote, what Microsoft is doing is entirely logical and consistent with the past, and our current experiences.
My main problem is with cache coherency over shared assets. I do think that there is the eternal lock/flock/lockf problem here, along with file timestamps. Microsoft don't have to care about that because they intend almost all interactions to be mediated through them, via APIs which can impose some cohesive behaviours. But, as a general model "all my files are in the cloud" gets really interesting when people have to work disconnected on shared product and then re-attach after e.g. a transatlantic flight offline, to try and re-sync things.
If somebody offered "FreeBSD desktop in the cloud" or "OSX in the cloud" or "Linux in the cloud" as well wrapped up, I'd consider it on it's merits.
Chromebooks are, after all "Google (which is in the cloud) in the cloud" aren't they?
I wonder how this translates in "but I paid $129 for a perpetual licence to word" -yes you did, but alas now you can't use it on this cloud-desktop quite as well as you'd like because.. well we didn't design it to work with your licenced copy of perpetual local-file word.