I have a feeling that Microsoft was (and is) groping its way toward dealing with Ajax in much the same way as other large enterprise shops: One part skepticism, one part resignation, one part enthusiasm, one part opportunism-probably lots of other parts, all represented by people or factions within the development organization. Lots of voices singing different parts and not always in harmony.
For Microsoft, Ajax has been a pimple on the elephant's ass almost from the beginning. Yes, Microsoft had a hand in some key components of Ajax. Yes, Microsoft has long understood that traditional HTML applications suck. But for a while the rampant interest in Ajax seemed to take Microsoft by surprise. The attitude seemed to be, 'Well XMLhttprequest is our contribution and sure we've been using elements of Ajax forever, but we've never considered it all that important. Our world is a lot bigger than Ajax.'
I'm not going to be a cheerleader for Ajax or even for rich internet applications because good user interfaces are sufficiently seductive in their own right. I think enterprise IT people know that a good user interface is important. But so are good database connections. So is security. So is effective implementation of business rules. Among other things and other contexts.
As this is a new blog on the Intelligent Enterprise Blogosphere, I'll try to define it by keeping an eye on Web 2.0 technologies as they relate to enterprise software. Rooting and snorting among the information bins of the IT industry can produce less than obvious insights-something I've been committed to doing for almost thirty years.
Nelson King has been a software developer for more than twenty-five years. Further complications include being a computer-industry analyst, product reviewer and author (of nine books on database programming). He's been writing for Intelligent Enterprise (and its precursors) for more than ten years. Write him at [email protected]Last month, Microsoft announced it had joined OpenAjax. When I read this tidbit, my first thought was "what else was there to do?" Then I asked myself, does this mean Microsoft is validating the Ajax juggernaut? Is this a symbolic milestone in the transition out of the hype phase for one of Web 2.0's leading elements? I suspect a number of IT managers might have similar questions.