The IT industry - always a seething den of buzzword bingo - appears to be in complete overdrive at the moment. Based on a back-of-an-envelope calculation, I believe I have had to internalize an average of 1.5 new buzzwords every working day this week.

Many of today's trendy buzzwords are Web related. This is not surprising. What I do find surprising is the extent to which modern buzzwords sound as if they were dreamt up in some high powered brainstorming session over in the marketing department.

Gone are the days of staid, acronymical buzzwords like HTTP or CSS. In are the days of punchy forget-me-not buzzwords like mashups and AJAX and Flash-enabled. Is it just me or does the current buzzword melange sound like it was inspired by a foodfight in a kitchen? All that mashing up going on before the AJAX[1] and the Flash[2] get to work cleaning things up...?

One thing is certain. A lot of the buzzwording going on surrounds improving the user experience on the Web. This sounds very laudable. How could anyone be concerned by such a thing? Are you worried? Probably not. Am I worried? Yes. A little.

Here is how I see it. Making an application easier to use almost always means making better use of the users ability to see; to hear; to click buttons; to access drop down menus and so on. Unfortunately, computers themselves cannot see or hear. This results in a most unfortunate inverse relationship. Namely, the more visual and interactive and compelling an application is from a user interface perspective, the harder it is to make said application do its thing without human intervention.

There is a pattern here. You could almost put it to music. In order to make end users want to use your application, it is necessary to make it visual and interactive. If you are successful, users get to the point where they want to hook up your application with some other application - to integrate them together. At this point, you are probably in trouble. The more successful you have been with your graphical user interface and user interaction, the harder it is likely to be to integrate your application with some other application.

A common buzzword in the industry is the concept of a "front end". In an ideal world, the front end just handles all the graphical user interface stuff while the back end does all the real work. In this ideal world, you can just bypass the front end and work with the back end directly when you want to integrate applications. Sadly, we do not live in this ideal world.

In the real world, front ends have a habit of becoming more than just front ends. They embed business rules and business logic without which, the back end cannot function. In short, the front end and the back end become inseparable. So much for the straightforward integration model. Think of the thick client applications on your desktop that you most like to use. Have they cleanly separated front ends and back ends? Probably not.

Think now of web-based applications you most like to use. How are their front ends and back ends? Well, historically, they have been quite cleanly separated. After all, a web browser only has limited capabilities. Behind the scenes it is really only capable of sending two commands GET and POST to things called URLs. Everything else (slight simplification!) happens at the back end.

Ah, but that was then and this is now. Now we have AJAX and JSON and Flash and the Google Web Toolkit and Windows Presentation Foundation and...

All these things help us to make web applications easier to use. In so doing, the clean separation between front end and back end gets more and more blurred. With every blurring of the separation, application integration becomes more complex.

There are a number of ways to view this. It could be argued that the price is worth paying. It could be argued that the price simply must be paid - it is the cost of a successful application. It could be argued that this is a terrible price and we should find a web development framework that does not sacrifice integration at the alter of interaction.

I'm feeling both pragmatic and world weary just at the moment. I'm going to view it this way:

- the price must be paid.


- as an industry, we can and should find a way to to make applications both highly interactive and highly composable.

[1] http://en.wikipedia.org/wiki/Ajax_cleanser


[2] http://www.pgprof.com/uk/html/uk_ki_flashcleanerspray.shtml

ITworld.com

• Email
• Print
• Share
  • Slashdot
  • Digg
  • Stumble
  • Reddit
  • Newsvine