[eluser]JayTee[/eluser]
[quote author="inparo" date="1203839201"]While I do think that the 'everything on one line' method chaining that their homepage advertises should be used with caution, what I was refering to here are the function/selector names. If you work with jquery everyday you will without a doubt get used to them. Since I only use it occasionally, I find it less than intuitive. Functions like 'one' and 'map; or selectors such as 'lt' and 'gt' really tell you nothing about their behavior.
It also makes it harder to read code in the future. You might use jquery now, but switch to a new framework down the road.[/quote]
For that very reason, I stopped even trying to use jQuery. I'm so used to Prototype, and the jQuery documentation is so hard to decipher (for me) that I find that I'm doing more searching documents than getting things done.
I've gone back to old Prototype code ("old" in computer terms can be as early as 2 years) and have been able to pick right up and figure out what I was trying to accomplish at the time I wrote it. When I look back at a few of the old jQuery things I've done, I inevitably have to go back to their documentation. It's just not as readable (for some functions) to me.
Again...it's a matter of preference. If you're willing to stick with a library for your projects, go for it. If you have to switch back and forth, I find that going between Prototype and jQuery to be difficult. If you like your homegrown library - use it. There have been projects where all I really want is to stop typing getElementById and put in my own version of the dollar$ function. It's easier than including the whole lib
