There is more than just noConflict .
jQuery is an intrusive library. It adds an internal jQuery123 value (for some randomized value for instance 123 ) for each element it touches (something like data or event handlers, among other reasons). In IE, this property is also reflected as an attribute.
So, if MooTools or any other library (or, indeed, a simple DOM method) comes in and starts messing with these properties / attributes or clone elements or hacking innerHTML , they are likely to spoil these supposedly unique identifiers, which is why jQuery gets confused and starts to behave erroneously as it is unusually difficult to debug.
jQuery also hid a bunch of event code to try and get the submit / focus / blur / focusin / focusout / mouseenter / mouseleave events to work and bubble up in browsers. This may confuse the code of another library that does not expect it.
So, with jQuery 1.4, you can just walk away using a different library at the same time if they work on separate elements that do not interact with each other. (jQuery 1.3 was also much more messy about what elements it touched.)
But overall, I would not recommend two main structures on one page.
bobince
source share