• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Toolkits vs self written

 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
 
Ranch Hand
Posts: 54
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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

 
Sheriff
Posts: 67746
173
Mac Mac OS X IntelliJ IDE jQuery TypeScript Java iOS
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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 ]
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic