Re:Google's Chrome OS is a Commitment Mechanism
by pvg on Monday December 28, 2009 @03:16PM
(#1019291)
My 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.
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.