File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes HTML, CSS and JavaScript and the fly likes Need Your Opinions On JavaScript Libraries 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 "Need Your Opinions On JavaScript Libraries" Watch "Need Your Opinions On JavaScript Libraries" New topic
Author

Need Your Opinions On JavaScript Libraries

Eric Pascarello
author
Rancher

Joined: Nov 08, 2001
Posts: 15376
    
    6
I know a few of you use JavaScript libraries. For those of you that do use one:

What library did you choose to use in everyday development and what was the major reason you picked it over the others.

If you were "forced" to use it, would you still use it? What do you like or hate about it?

Thanks,
Eric
Bear Bibeault
Author and ninkuma
Marshal

Joined: Jan 10, 2002
Posts: 61770
    
  67

jQuery, for many reasons, but primarily because of its power, and the manner in which it emphasizes Unobtrusive JavaScript and clean page design.


[Asking smart questions] [Bear's FrontMan] [About Bear] [Books by Bear]
Hussein Baghdadi
clojure forum advocate
Bartender

Joined: Nov 08, 2003
Posts: 3479

jQuery.
Beside of what Bear said, jQuery enjoys a lot of plugins (not to mention Bear's book on jQuery )
nimo frey
Ranch Hand

Joined: Jun 28, 2008
Posts: 580
..and what about prototype?
out of date?
not powerfull enough?
not much plugins than jquery?
not faster and more stable than jquery?

I miss the facts:-)
[ November 25, 2008: Message edited by: nimo frey ]
Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 42950
    
  72
Prototype. I like the ease of use of its Ajax.* methods (which is all I use it for). If I needed DOM features I'd evaluate jQuery in addition to Prototype, but the need never came up, so I'm happy with it.
Bear Bibeault
Author and ninkuma
Marshal

Joined: Jan 10, 2002
Posts: 61770
    
  67

Originally posted by nimo frey:
..and what about prototype?
Prior to jQuery, I used to like Prototype. My enthusiasm has waned considerably.

We used Prototype in a web application with a complicated GUI that sported many levels of nested iframes to achieve its goals. In this environment, Prototype increasingly kept getting in the way more than it would help. The intrusive nature of Prototype (it modifies the DOM elements and JavaScript objects when it loads) started leading to weird and hard-to-debug problems in the cross-frame environment (really weird errors like "Prototype is not defined" within Prototype's own code) and made it hard to use other JavaScript libraries, as well as the JavaScript that we'd write ourselves.

When a tool starts creating more work than it saves, it's time to move on.

Originally posted by nimo frey:
out of date?
Many people think so. I've heard more than one person refer to it as a dinosaur.
not powerfull enough?
Too intrusive (see above).
not much plugins than jquery?
jQuery was designed for plugins. Prototype, not so much. And no library has the plugin community that jQuery has.
not faster and more stable than jquery?
They're both fast, but see above for my assessment on stability.
[ November 25, 2008: Message edited by: Bear Bibeault ]
Eric Pascarello
author
Rancher

Joined: Nov 08, 2001
Posts: 15376
    
    6
One of the thing I have to research a lot with the plug-ins/widgets is Accessibility. Where I work, it is a BIG thing and I tend to find a bunch of toolkits out there do not cut it.

Try to use a screen reader on some of the widgets out there and it is like listen to finger nails on a chalkboard.

Some of the widgets in JQuery make me feel like some kid wanted to become famous and wrote a useless piece of code. Others are well done. It is like picking your poison.

With other libraries that have widgets built in, you sort of feel safer that it was tested in a more professional fashion, but you are sort of handcuffed to using it.

To me the biggest thing is the core. I like JQuery's core and prototypes has seemed to have improved since the last time I used it. JQuery and Prototypes XHR code sort of scares me in with things I know what happened in production and their code does not cover those safety precautions that I tend to take.

Eric
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Need Your Opinions On JavaScript Libraries