Hello, For me the problem is actualy Why are you using Prototype when jQuery is more efficient, intuitive et en plus more developed? And remember you, jQuery accept other library with .noConflict() And you can manage RoR with jQuery http://jimneath.org/2008/06/18/using-jquery-with-ruby-on-rails.html
So for me try to do something with Proto is a challenge because jQuery is so smart. cordialy LV On 1 mai, 02:45, "joe t." <[email protected]> wrote: > The short answer is that there's no short answer. There's not really > anything that either library can do that the other can't. It's mostly > a question of the requirements of the project, or familiarity with > either library's approach, etc. > > There's no conclusive answer & any answer you do get will be loaded > with facts about each, but no single knockout argument to use one or > the other. > > -joe t. > > On Apr 29, 2:22 pm, kstubs <[email protected]> wrote: > > > > > Why Prototype over JQuery? I am an avid fan of Prototype and have never > > used JQuery, but JQuery seems to be so popular. Is it just that, popular? > > I love prototype, and learning something new and magical every day it > > seems, but is there something *better* that Prototype does that JQuery > > doesn't, or vice-a-versa? > > > Karl.. -- You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
