November 23, 2009

The miracle of Web apps gone wrong

Browser-dependent Web applications were never a good idea, but now it's gotten out of hand

Remember when Web-based applications were going to save us all? Nothing to install on the local system, quick and easy access, centralized security, lower TCO, and a bevy of other big benefits. Ah, those were the days. Unfortunately, it seems that those noble ideals were co-opted by the same type of mediocre programmers that made many thick apps such a disgrace -- they managed to take a framework that should have resulted in far fewer IT headaches and turned it into a worse situation than before.

Here's an example. Vital Application A was built specifically for Internet Explorer and will not work on any other browser. In fact, it was built specifically for IE 6 and will not work with IE 7 or IE 8. Vital Application B worked fine with IE 6, but a recent upgrade broke that, and it will now only work on IE 7, but only as long as nearly all the security protection settings are turned off. And so on, ad nauseum.

[ Discover what's new in business applications with InfoWorld's Technology: Applications newsletter and Killer Apps blog. ]

It's an impossible position. There's no way to make this work reliably and securely. In fact, it's likely that browser-specific stipulations such as this will be more responsible for future IT application choice and direction rather than features and cost. Too bad if a new application is cheaper, simpler, and richer in features -- if it cannot run on the currently installed user browser, you're out of luck.

So how did we get here? Simple: Laziness, time, and a disturbing reliance on closed frameworks. It's probably accurate to say that if anyone was going to start building an enterprise Web application at this point in time, they'd head straight for an AJAX foundation -- at least I hope so. But that wasn't available eight years ago when the application was developed. Now the app is at Version 9.45, and it's an ungodly mess of ActiveX controls and patchwork .Net code. The application vendor has probably had several meetings to discuss the possibility of rewriting it from scratch to alleviate the constant break/fix cycle caused by the legacy code, but it's just not feasible in this economy.

And there we are.

Users are confused, too. They see what's happening whether they understand it or not. They use eBay; they use Facebook and Gmail and sites driven by Drupal all the time. Then they look at the applications they have to use day in and day out that resemble an Edsel in comparison. They know enough to use Firefox at home, but they're forced to use IE at work. Users may not be IT people, but they notice things that affect their daily functions on a fundamental level.

additional resources
White Paper - How to Improve Delivery of Advanced Web Applications

White Paper

Virtual Workforce: The Key to Expanding The Business While Cutting Costs

Get the independent advice and expertise you need to support a virtual workforce.

Go inside:
The three-step approach to making a virtual workforce a reality.
The four flavors of client virtualization technologies.
The three key initiatives that solve IT challenges.
Download now »
White Paper: Successfully Secure Your Wireless LAN With Wi-Fi firewalls.

White Paper

Addressing Linux Threats Leveraging Fewer Resources

The increase in Linux popularity has increased the frequency and sophistication of malware attacks. Read this 2 page white paper now to learn how you can protect your Linux environment with real-time protection that is certified by all major Linux vendors.

Download now »
White Paper - The 2009 Handbook of Application Delivery

White Paper

The 2009 Handbook of Application Delivery

Ensuring acceptable application delivery will become even more difficult over the next few years. As a result, IT organizations need to ensure that the approach that they take to resolving the current application delivery challenges can scale to support the emerging challenges. This handbook elaborates on the key tasks associated with planning, optimization, management and control and provides decision criteria to help IT organizations choose appropriate solutions.

Download now »
White Paper - Is Your Backup System Outdated?

White Paper

Mid-range Storage Considerations

A common misconception is that mid-range storage requirements are dramatically different than that of a larger enterprise. Mid-range storage users may require less capacity, but they have similar functionality and management requirements. This ESG paper examines mid-range storage needs and reviews a new solution that adjusts size while retaining value, performance and functionality.

Download now »
aaugh 23-Nov-09 4:47pm

Most new internal browser-based apps built today will suffer the same fate down the road, regardless of framework or technology.

Pay now or pay more later. Guess what the choice will be, especially in these straitened times?

starpilot 24-Nov-09 1:46pm
Let's see the cause for web-app failures - Lazy Programmers, Hmm? Why not put the blame first on the greedy marketeers that promise everything in the world delivered in microseconds to extort hard cash from the technically challenged but rich customer? Once the 'mark' is hooked, they skip off to the next 'mark' and leave the development work to the chinese engineer who doesn't speak the customers native language to develop the product from specs/requirements they don't qute understand. Or how about blaming the brilliant 'Software Engineering Gods' who created the eternally confusing object oriented languages so that they could hide the intimate details of the program components and what they really were doing was hiding their own incompetence in understanding the complexity of the real world behind arcane and uselessly complex computer constucts or showing off their virtuosity in the construction of arcane structures. Or how about all those computer genuises that create a new language because they can't figure out how to make the current one work? Or the OS vendors that need to create 'new' incarations of old products to keep their revenue stream alive? Or the new programming team that throws out the 'old bathwater and the baby' to make an improved version that works better in the new way but isn't backward compatible with what the external community has? In the hardware world, many new products at least try to be backward compatible with previous incarnations, in SW if its old and it worked it has to be improved and then broken so that it can really be improved!
BigRonG 30-Nov-09 12:23am
I think I am with starpilot. It seems to me that greedy browser manufacturers haven't given sufficient planning or thought to their products. The result is an inability to write an app that can be 'universal'. The 'hooks' that the story refers to are every thing from security items to display issues. MS has gotten the software world used to 'good enough' as opposed to the old Unix 'rock solid' standard. 'Good enough' might make a ton of money for the original manufacture - but it just means a ton of pain for the developers working on the system. Pfft - I remember major projects failing because VB 3 didn't have critical abilities. It brings to mind the question about where to draw the line between draft/beta and release.

Today's Headlines: First Look Newsletter

Find out what will be news for the day, with our first-thing-in-the-morning briefing.

©1994-2010 Infoworld, Inc.