Revival of the FattestProgramming Posted by Petter Hesselberg Wed, May 09, 2007 10:29
In search of the Unholy Grail or Why Web Applications are Evil
Java Web Start, from Sun, is an application deployment technology that lets you download and install Java applications without the traditional installation and upgrading hassles and without compromising security. In a similar vein, Windows Installer combined with .NET assemblies allows on-demand installation and upgrading as well as a secure execution environment (sandbox).
Real applications (fat clients) have many benefits over web applications (thin clients). They have much richer and more responsive user interfaces (including, but not limited to, drag-and-drop, and integration with the desktop and with other applications), they can run even if the browser does not, they are less dependent on connection speed, and they let you work offline.
In 1997, around the time NCs failed to save the world, the applet-based Corel Office for Java was a miserable failure. How usable would Microsoft Office be as a suite of web applications? I’m writing this in Microsoft Word; if I had to do it in a web-form text field I would go mad.
In an interview with InfoWorld last year, Alan Cooper said:
Whatever the color of the fish, it is certain that the browser was designed to disseminate hypertext, not to serve as an application platform. Over the years, an amazing plethora of duct tape, chewing gum, and paper clips has been invented to rectify this, starting with the original CGI specification. Later came more efficient ways to extend the web server — first ISAPI and NSAPI, then seriously clever stuff like ASP and JSP, which mixes HTML with VB or Java, the HTML itself mixed with various incompatible client-side scripting languages operating on various incompatible DOMs. The browser expanded its understanding beyond scripting languages and DOMs to include embedded objects (Java applets, ActiveX controls), and client-side cookies help manage a sort of “meta-session” on top of an inherently sessionless protocol.
Rube Goldberg would’ve been proud.
Mixing presentation and content is inherently evil; it gets in the way of effective maintenance. And, just like the Pleistocene 3270 terminal, the browser application reloads the entire screen on each push of a Submit button — an extraordinary wastefulness of bandwidth.
The entire hypertext navigation paradigm of the browser is hostile to applications. By a formula I just derived, 82.5 percent of all web application development is spent fighting the confusion of the back button, the difficulties of multiple browser windows, and the evil of HTML frames. And double-clicks! We’ll never know how many bills have been paid twice because of an inadvertent double-click.
Now fat clients are making a comeback, and it’s time again to start thinking about “what we could do as a civilization.” (Cooper is always modest in his phrasing.)
Then we can go back to using the browser for its intended purpose
This was written in 2002; the original is here. And in spite of new advances in duct tape technologies, chewing gum methodologies and paper clip mythologies, the basic paradigm mismatch remains and shows no obvious signs of imminent departure.
Back then, a reader pointed out that the term "rich client" is preferable to "fat client". I completely agree. But it would sure screw up the title of the piece: Survival of the richest?