3 ms·
The problem with this is the great deal of uncertainty about when (if ever) the 'optimal' outcome of the commitment will occur. It's not just a matter of applic
by pvg 17y ago
The problem with this is the great deal of uncertainty about when (if ever) the 'optimal' outcome of the commitment will occur. It's not just a matter of application availability as the author seems to imply.
Even if CloudPhotoShop and CloudEmacs materialized tomorrow, until there is ubiquitous high-bandwidth connectivity, most users will want to continue to make lots of fine-grained choices about what particular bits of their data they want stored locally, remotely, remotely-with-local-cache, etc. There's no way for my CloudApps to know in advance that tomorrow I'll be on a 15 hour flight so I'd like to have these 2 movies, 10 playlists and the latest versions of a couple of Cloudocuments I last edited from a different machine in my local storage before I lose connectivity.
- mmastrac 17y agoStorage is cheap though, so this only becomes an issue when you want to cache gigabyte sized movies. Why not cache your whole photo and music collection now? In 10 years you won't even worry about huge videos. You'll be carting around terabyte sized flash in your phone and more on your cloudbook SSD.
- pvg 17y agoBecause there is no user-controlled local storage under ChromeOS, at least as described now. But even if there was, no matter how much local storage you have (and the assumption is that you'll have more on the cloud and your cloud dataset size will be larger than local storage) you'll still want to make explicit storage decisions based on the availability of bandwidth and connectivity. Say today at the office I worked on a few documents, shot a gig of video at the office holiday party, bought a couple of mp3s. All were stored on the cloud. Tomorrow morning I, before I leave for a disconnected mountain cabin, I fire up my netbook and tell it to sync. I don't have time to wait around for the video but I specifically want the docs and the mp3s. Additionally, I want an explicit sync of a group of documents from two years ago. They're in the cloud but I have no idea whether they are in the netbook cache so I want an explicit check. The only way you'd stop doing this sort of thing is if you're more-or-less always connected.
- orangecat 17y agoExactly. I reject the entire premise that web apps are fundamentally "better for you". Yes, they have zero installation, and that's great. There are also a number of drawbacks that the author ignores or glosses over, such as requiring ubiquitous high speed (and often low latency) connections, having all your data in the hands of a third party, and apps being written for the lowest common denominator of HTML/CSS/Javascript rather than taking advantage of advanced OS functionality. Both web and local apps have their place, and there's no need for one type to dominate.
- GHFigs 17y agoI reject the entire premise that web apps are fundamentally "better for you". You're inserting the word "fundamentally", but the author is not claiming they are fundamentally better than native applications at all. Not every article is "X vs Y". His premise for talking about commitment mechanisms is that you've already decided that web applications are the long-term optimal choice for you. If it isn't the optimal choice for you, the commitment mechanism is meaningless.
- stanleydrew 17y agoThe uncertainty will surely mean that Chrome OS will remain a secondary OS for many people (including me) for awhile. But over time as you realize that 80%, then 90%, then 95% of what you actually use is available as a hosted app, Chrome OS (or the MS or Apple equivalent) becomes your primary OS.
- GHFigs 17y agoThe lack of "ubiquitous high-bandwidth connectivity" is likewise a short-term cost, and may already be negligible depending on how ubiquitous you need it to be and how much bandwidth. It's already good enough for many if not most people, and the gaps are shrinking.
- pvg 17y agoMy point was users will always want the option of explicit storage control (which ChromeOS lacks) until local-to-cloud syncing is essentially transparent. This takes a a lot more bandwidth and ubiquity than is currently available. A reasonable technical analogy is the use of overlays (user controlled) vs virtual memory (automatic) by programmers - until hardware support, memory and disk sizes and speeds were available, overlays were the practical and desired memory management technique. Similarly, the cloud has to be much closer in availability and access speed to local storage before users don't have to bother with much explicit control of data storage location. I think that's a lot further off than the author and you assume.