On CHOW: Should that woman be drinking?
BNET Business Network:
BNET
TechRepublic
ZDNet
TalkBack 16 of 16:
« Previous
Portable Application Environments
Coming soon to a desktop near you! Instead of the battle royal we've been bracing for, the one between J2EE and .NET frameworks, we can now see clearly that the portable runtime engine wars have evolved into something much larger. The portable application environment.

Two key concepts that have long defined the computational box that entraps us all are being diminished here - the importance of the underlying operating system, and, the integrated stack model that drives the frameworks (J2EE and .NET). Combine the emerging Eclipse developer layer with IBM's portable WorkPlace environment, and you have a very robust target developers can reliably write too. It's a target without the platform specific baggage that has long plagued application developers. Yet, it's able to provide the same elements of accelerated development promised by platform specific integrated stack models. And it does so in a way that is consistent with the open interoperability model of open standards, open interfaces, open communications and messaging protocols, open XML technologies, and open class libraries (hello Sun!).

While it may seem that portable run time engines led the way, riding above the distro layer, i think the historic moment came when Netscape's Marc Andressen referred to the many versions (distros) of Windows as ?just a bag of API's to write to?, and then went on to prove it could be done. The portable application became the cross platform distribution channel for both Java and, portal based web applications.

Netscape's XPFE web application model is still cooking (XPCOM and XUL), but the challenge to any community in providing a portable rich client environment are staggering. This is going to be a cross community effort, or, the effort of a cross community assembler such as demonstrated by IBM's WorkPlace or Sun's Java Desktop. The assemblers have a much better grip on this space than the core communities who are just now getting about the business of coordinating their efforts (the recent meeting between Mozilla and GNOME as an example). But that's not to say the assemblers themselves have problems keeping their proprietary heritage in check. Red Hat is forever under suspicion. Sadly Sun choose to release the Java Desktop bolted to their chosen Linux distro, instead of unleashing it as a portable application environment. The good news is that it doesn't look as though IBM will make the same mistake with WorkPlace. And no doubt Ian Murdock of Progeny fame is watching the portable application environment space too. His Dell model of made to order assembly could move to providing a distro independent application environment that challenges both WorkPlace and the Java Desktop in ways that unleash extraordinary dynamics.

The ongoing activities and synergies between core application communities and frameworks communities are for the most part beneath the radar. But they deserve mention in any discussion about Eclipse. Distribution to the desktop is critical. But so is the way in which the environment is managed and maintained. Microsoft's iron fisted control over interdependencies, protocols, libraries, components, interfaces and methods insures that the integrated stack environment will be managed and maintained. It also insures that all the profitable opportunities belong to Redmond. So MONO is a much safer target to write to than .NET because it is open source, and ?open opportunity?. Developers still have access to the Windows XP platform without having to disrupt or re engineer the end users environment, but their not completely hostage to the vagaries of Chairman Bill's permission based interoperability model.

The Python community also looms large. Like MONO, they don't have as yet a desktop distribution method that can compare to Mozilla ? one where the open application environment is put down as part of the browser install, managed and maintained by the community rather than rogue developers and hapless end users. This is certain to change once the Chandler project reaches their 1.0 release. Chandler promises to not only deliver (and maintain) the Python environment, wrapped in the interface of a much needed cross platform PiM/Project Management application, but also an underlying Sleepycat XML database resource management system that can be used by other applications and services.

Someday some smart guy is going to bundle OpenOffice.org with NetBeans (and all those wonderfully rich J2SE class libraries), and similarly deliver a rich Java based environment to the desktop that developers can reliably target. The key again being rich client side resources managed and maintained by core communities so that dependencies and version controls avoid the possible anarchy of rogue developers and hapless end users having to carry the responsibilities of maintaining the environment.

Hopefully at JavaONE IBM will fully disclose what they intend to do with WorkPlace and Eclipse. If distributors, developers, and adventurous end users can put down a single rich client application environment that works similarly across many platforms, there might be a chance of reaching the kind of critical mass needed to pry loose the iron grip of Redmond. But so far IBM has yet to do the kind of things necessary to signal the world that they've thrown down the gauntlet and are serious about backing a truly open portable application environment. Things like returning their WorkPlace improvements to the core application communities - like OpenOffice.org. I wonder what they're waiting for? The Eclipse project was a boon to IBM's WebSphere business and services model. Why not wreck havoc on the desktop using the same play book? Time will tell, but hard not to notice that pieces are falling into place. Maybe in ways not planned.

~ge~
gary.edwards@OpenStack.us
Posted by: garyedwards@...   Posted on: 06/22/04 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

Yawn, another wannabe...  No_Ax_to_Grind | 06/21/04
yes, of course  doh123 | 06/21/04
I don't like .NET  voska | 06/21/04
Isn't .net what you get when you couldn't get a .com?  B.O.F.H. | 06/21/04
lol ... good 1  oldskool | 06/21/04
Dangerous to use ZDNet as your only source of information  Richard Flude | 06/21/04
Windows desktop apps in Java ???  worknman | 06/21/04
Not exactly  quietLee | 06/21/04
Yes, in Java  Richard Flude | 06/21/04
I don't get it  rapson | 06/21/04
IBM Lock in is what  quietLee | 06/21/04
BS  Richard Flude | 06/21/04
Give it a go  Richard Flude | 06/21/04
Eclipse provides an application framework .... it manages code!  oldskool | 06/21/04
Looks interesting!  Linux_Developer | 06/21/04
Portable Application Environments  garyedwards@... | 06/22/04

What do you think?

SponsoredWhite Papers, Webcasts, and Downloads

advertisement
advertisement

SmartPlanet

  • Thought-provoking progressive ideas on diverse topics that intersect with technology, business, and life, and matter to the world at large. Visit SmartPlanet
  • More from IBM
  • Innovate your business' process model, play against the market, compete against others on our scoreboards and WIN! Try INNOV8 2.0: A BPM Simulator
  • Enabling Real-World Business Transformation through IBM Service Management Read the EMA Analyst Report
Click Here