wood burning stoves*
The moose likes HTML, CSS and JavaScript and the fly likes Toolkits vs self written Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » HTML, CSS and JavaScript
Bookmark "Toolkits vs self written" Watch "Toolkits vs self written" New topic
Author

Toolkits vs self written

Ian Link
Greenhorn

Joined: Oct 13, 2006
Posts: 4
We are currently evaluation various options for AJAX development within my organisation. There are two groups of though that seem to have emerged. One is for self written code and the other is for the use of toolkits. What are peoples feelings about the pros and cons of each of these approaches?

Thanks

Ian
Sapna Grover
Ranch Hand

Joined: Sep 27, 2002
Posts: 54
When you write the raw JavaScript yourself means that you are on your own. You have to deal with browser incompatibilities and start from scratch.

Using libraries on the other hand provides following benefits -
a. Fast development
b. The JS code is well tested hence less.
c. Rich feature set.
Andreanes Yosef Vanderlee
Greenhorn

Joined: Mar 30, 2007
Posts: 12
For more than a year, I always use self written code, coz I think it's more flexible (and of course we need an extra work too).
But, using another toolkit is good enough (I've tried GWT). We don't need to think about the browser compatibility, memory leak *I'm sicked with this*.
Dunno with the other..

--
Andre

Originally posted by Ian Link:
We are currently evaluation various options for AJAX development within my organisation. There are two groups of though that seem to have emerged. One is for self written code and the other is for the use of toolkits. What are peoples feelings about the pros and cons of each of these approaches?

Thanks

Ian
Bear Bibeault
Author and ninkuma
Marshal

Joined: Jan 10, 2002
Posts: 60780
    
  65

It's a good question. Personally, I tend towards the "write it yourself" camp. That way, you have complete control over your codebase and there are no surprises. However, I also believe in not re-inventing the wheel unless you are going to invent a better wheel.

That's why I'm a fan of libraries such as Prototype and jQuery, but a serious denegrator of behemoths such as Spring and Struts. The former help me get my job done without getting in the way, but the latter just add layer upon layer of complexity that end up making things much more difficult and complex than they need to be.

So I pick and choose which toolkits I employ carefully. I will only use toolkits that help me get my job done quicker without getting in the way, or imposing their own set of restrictions on how I can write my code.

To the subject of this weeks' book promo, I think it's madness to write Ajax calls without the aid of a library such as Prototype or jQuery. Dealing with the browser dependencies and low level status callbacks is a PainInTheKeester™ that these libraries handle nicely.
[ April 09, 2007: Message edited by: Bear Bibeault ]

[Asking smart questions] [Bear's FrontMan] [About Bear] [Books by Bear]
 
 
subject: Toolkits vs self written
 
Similar Threads
self taught
How to Convert DTD file into XFLAT file
Sample Webservices application
Soap toolkits
A book you can recommend for me...??