Wednesday, February 22, 2006

With Web 2.0, why'd we bother getting rid of mainframes?

Slashdot ran a story yesterday called Office Tools on the Web.

I don't get it. Except for the shared-document side of things, who wants to use a web browser as a word processor or spreadsheet? How annoying. I wouldn't mind having automatic backups of my stuff to the web, but I certainly don't have any desire to use a second-rate Javascript app over Microsoft Word or OpenOffice.

Debunking the why's:

Myth: The UIs are easier for non-technical people. All you need to know is a web browser.

Fact: It's far easier to make powerful UIs with traditional Windows and Mac components. The UIs are much more consistent on Windows or Mac as well, whereas every web developer has to be clever to figure out how to get reasonable interactivity out of a web browser. All computer users are aware of how to click a different icon to get processing.

Myth: The stuff is accessible from anywhere!

Fact: Sure, if their servers are up. The web is stateless, but unfortunately requires a connection exactly when you need it when you use it as an application. How often have you wanted to get to Gmail and had "Service unavailable" for 10 minutes or more? Using POP with Outlook or Thunderbird means you can get to your email when you need it, and just new email wouldn't arrive while the connection is down.

Myth: More reliable! No more having to back up your hard drive?

Fact: If you believe this, you haven't tried using any of these. You obviously never have lost something you've typed for hours into a Gmail or Blogger window and then had Gmail crash and lose your work. Or you've never submitted something, had a problem with the web server, then try to go back to the last webform with the back button and see all of your typing lost.

The bottom line is, by accepting Web 2.0, we're back to the mainframe days, except with with less reliability. Did you know that a <1% failure rate is considered acceptable to a lot of these web companies? Can you imagine of 1% of Word users were losing their work lately, what the outcry to Microsoft would be?

Thanks, I'll take my desktop apps. I wouldn't mind having web-delivered applications, like Avalon/XAML or Java Webstart promise. I don't mind them as long as they can use IsolatedStorage to store stuff on my local disk, then back it up to the server later. What I really don't need is waiting on a less reliable central server than an AS/400 to write a Word document just so someone can put ads in front of me.

PS - I just lost a big section of this message because Blogger didn't properly interpret the less than sign, thus trying to make it into an HTML tag. These web apps are for the birds.

1 comment:

eighties said...

Considering that the average annual failure rate of disk drives is 2%-4%, a 1% failure rate for web-based applications seems completely reasonable.

source: http://www.pcworld.com/article/129558/study_hard_drive_failure_rates_much_higher_than_makers_estimate.html

Even better example from Amazon AWS:

"Amazon EBS snapshot can expect an annual failure rate (AFR) of between 0.1% – 0.5%, where failure refers to a complete loss of the volume. This compares with commodity hard disks that will typically fail with an AFR of around 4%, making EBS volumes 10 times more reliable than typical commodity disk drives."

source: http://aws.amazon.com/ebs/


I happily store data 'in the cloud'. I'm also not too scared that Amazon or Google are going to shut down their servers any time soon. If that ever does happen, I'm sure I'll have plenty of warning time to move my data elsewhere.