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.
Originally posted by nimo frey: ..and what about prototype?
Prior to jQuery, I used to like Prototype. My enthusiasm has waned considerably.
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 ]
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.
It's exactly the same and completely different as this tiny ad:
Programmatically Create PDF Using Free Spire.PDF with Java