When AJAX aint right for the job
JavaScript/AJAX isn’t always the best tool for the job. Over the last 2 years, I’ve been the principal developer on the CRM project at work. For most of that time, it has primarily been a Javscript, Web-enabled application.
Recently, we have realised that we’ve hit the wall with what is possible with JavaScript and HTML (especially when the target platform is IE6+). We are now moving to the Java-based RCP (Rich Client Platform), which is part of the Eclipse framework.
I believe that JavaScript frameworks have a place, but I do not think it is within enterprise-critical applications. When the environment is controlled and scalability and performance is a factor, you should carefully consider your options before joining the AJAX bandwagon.
Comments
Comment from Darryl Lyons
Time: August 25, 2007, 9:08 pm
Rey, I think that you have to take what I said in the context of my experiences. I have been building a ‘desktop application’ in the browser.
It is my opinion that you will always be able to build quicker, more scalable solutions in compiled languages than you can with something that sits on top of a browser. I don’t think anyone can argue that RCP provides a much richer framework than any JS library out today (including Ext).
Also, my experiences are largely with IE. We have a large terminal server user base. Memory usage is a consideration. IE with a blank page starts at 50MB — and then you add JavaScript files and then DOM elements to that, you are talking about a sizable memory footprint for a SMALL application.
Comment from Rey Bango
Time: August 25, 2007, 8:22 am
Hi Darryl. I beg to differ. Ajax frameworks such as Ext, Tibco, JackBe and Zimbra have all been built to work within the enterprise and have the clients to prove it. I’m not doubting your statements about specific troubles you’ve had but I (and I think others) would like to understand the limitations you’ve encountered. You might be surprised by the feedback you receive.