Duking it out over AJAX
Numerous posts in the news regarding AJAX have sparked an interesting debate:
Which toolkit should I use?
Easy enough to ask, not so easy to answer. The sprawling growth of AJAX toolkits has reached a point of dilution. There are so many packages that claim to be THE toolkit it makes it almost impossible to choose one. Additionally, as this technology (as a framework) is so young, the changes are rapid. This can make development a little tedious with the constant need to synchronize changes from your source tree to the package you are using.
AJAX code is very, very simple to write. A simple app that qualifies as AJAX can be composed an deployed in a few minutes…even without a Framework. However, this introduces an interesting opportunity for talented developers and large companies to build a complicated Framework/toolkit that does nice things for you like standardize widget interfaces, integration, and deployment.
It should be easy to use a GUI composer style app to build an AJAX app. Well, at least “most” of the UI. The backend, well, that’s another story. Some of the backend can be build on existing Web Services technology.
Is there an IDE or a Development Framekwork/Toolkit that works for both front-and-back end? Aside from .Net there is very few development environments that address front/back end. If you choose Java, you must choose between JBoss, WebLogic, WebSphere, Tomcat, or a host of other application servers. Then you must pick what you will use for front-end development (UI). Already, if you are not married to .Net, you are saying something like, “I will use Eclipse.” Ok, what if you use PHP, Ruby, or Python? What IDE will you use? Okay, so you are still saying, Eclipse.
Well, now, what framework will you use to tie front and back end development together?
This is what Open AJAX is all about, bringing both sides together. Regardless of what language you use. PHP, Java, Python, Perl, Ruby, C/C++. Basically, there is little or no need to build anything for .Net since that case is handled by default.
Now, you see IBM, BEA, and a host of others forming ranks to square off against Microsoft. They know that if it’s easier to build better apps on a MS platform, they will lose customers and users, and thus deminish. Same goes for MS, if it’s easier on another platform, that’s bad for business.
Google is sort of hiding in the shadows. This means:
a) They are up to something
b) They are waiting to see who’s going to win before they side
c) They have already sided and are trying not to cheese the other side off
Either way, as a developer, you’re going to win. The users will win. 21st century applications will be different than 20th century net apps. The Request/Response paradigm is quite powerful, and simple - I also recognize Streaming protocols are powerful and required as well. For the sake of this post, however, making a Req/Res transaction seem invisible is what this wonderful thing called AJAX is all about.
Which side are you on? .Net or Brand X? Write in and let us know.