Honestly, I see it as just an extension of the thin-client model. Mainframes went out of usage because personal worskstations were better for most purposes. Now, the centralized model is being trotted out again, because technology allows it to work better for some things, such as universal data access.

In the end though, many services are not so much about the software itself, it is the people connected to them, that make them desirable. Sure there will be crackers, but building the next Facebook, even if shinier, is not enough. Then there is experience with the software and the related support.

So I guess there will be more types of platforms and software, open and commercial, hacked and cracked even. The times they are a-changing.

Personally, I'm waiting for the day when I get a true VR web experience. An interactive web, glorious vistas of code, sweeping and swirling in front of my eyes. Not quite the Matrix, where everything is seen as code, but a mixture of solid objects and the underlying code.

Not only is it the same as before, but we have an added problem. Mainframes used to be used pretty much exclusively for work/study, and more often than not, the employer/university also ran the mainframe.

But now the usage model is completely different. From online banking to social applications, the data stored is far more sensitive and personal, (In effect, you entire life can now be traced from your laptop) and with cloud applications, you lose data ownership. Serious problem. until that is reliably addressed, "the Cloud" seems like a very bad idea if you care about privacy.

And with the EULA you have to sign, if something goes wrong, you are completely S.C.R.E.W.E.D.(TM)

It's why I'm still lukewarm about Google Wave. Instead of storing the emails locally, they're stored on your wave provider's network. (which isn't necessarily bad. it is the same as a conventional gmail account) but for some situations, you really want to preserve data ownership. (Which means that you have to run your own *something* server, and more often than not, that simply isn't allowed by the providers, so you have to build from scratch (At least google got that right. open sourcing the protovol makes the thing paranoid-friendly))

« Last Edit: November 17, 2009, 02:34:28 PM by dark_dragon »

Logged

"Reality is that which, when you stop believing in it, doesn't go away."-Philip K. Dick

All I know is I thought Ubuntu One would be the shiznit, but it sucked ass. Not a fault of the cloud (guess it uses Amazon's) but because the sync sucks bad. So I installed dropbox. So now the files I like to update a lot are easily shared between computers and I can sneak to them through work all because of this fabulous cloud thing you speak of.

Not only is it the same as before, but we have an added problem. Mainframes used to be used pretty much exclusively for work/study, and more often than not, the employer/university also ran the mainframe.

But now the usage model is completely different. From online banking to social applications, the data stored is far more sensitive and personal, (In effect, you entire life can now be traced from your laptop) and with cloud applications, you lose data ownership. Serious problem. until that is reliably addressed, "the Cloud" seems like a very bad idea if you care about privacy.

And with the EULA you have to sign, if something goes wrong, you are completely S.C.R.E.W.E.D.(TM)

It's why I'm still lukewarm about Google Wave. Instead of storing the emails locally, they're stored on your wave provider's network. (which isn't necessarily bad. it is the same as a conventional gmail account) but for some situations, you really want to preserve data ownership. (Which means that you have to run your own *something* server, and more often than not, that simply isn't allowed by the providers, so you have to build from scratch (At least google got that right. open sourcing the protovol makes the thing paranoid-friendly))