I just stumbled upon this link that lets you test the performance of selectors in different Javascript libraries:
http://jamesdonaghue.com/static/peppy/profile/slickspeed/ Prototype doesn't look very good from that tests and that's pretty much in line with my own feeling after having used JQuery for a while before being introduced to Prototype through Tapestry 5. This made me wonder if it would be possible to write a plugin for Tapestry that overrides the default Javascript library or wether Prototype is hardwired into the Tapestry internals? I haven't researched it in any way yet, but I'm aware that some mixins, client side validation and maybe even some core components would stop working since they depend on Prototype. Is there anything else that depends on it? Anything that cannot be overridden in a plugin? Could the client-side behaviors be abstracted away so that multiple implementations can be used? Just wondering if this would be possible and what it would entail, since tapestry 5 already allows so many other things to be configured, overridden or replaced. regards, Onno
