I’ve written before about my dislike of “the cloud.”
The term implies that there aren’t specific actors doing specific things with data, which will tend to weaken people’s impression that they have rights and obligations when using or providing cloud services. We’re talking privacy problems.
When “cloud” services fail, the results can be widespread and significant. Think of cloud computing as a sibling of security monoculture.
TechDirt’s indefatigable Mike Masnick reminds us of this with a tweet today about hiccups in Google Calendar that may have prevented him getting on a conference call. He’s written once or twice about the cloud in terms of legal/discovery issues, privacy issues, and business/regulatory hurdles.
Remote computing is not going away, but it’s a fad that should fade over time. I think I hit the right notes in an earlier post where I said:
There will always be a place for remote storage and services—indeed, they will remain an important part of the mix—but I think that everyone should ultimately have their own storage and servers. (Hey, we did it with PCs! Why not?) Our thoroughly distributed computing, storage, and processing infrastructure should be backed up to—well, not the cloud—to specific, identifiable, legally liable and responsible service providers.