I understand the argument for not trying to make MooTools compatible with other libraries and I agree with it.
My concern is when we as developers don't have any control over what other scripts are included, like writing a plugin for Wordpress for example. In situations like those, do I have to ditch MooTools for a more third-party-friendly library? It's not reasonable to push the compatibility problem onto the end-user. What do you do? I'm experimenting with adapters (similar to ExtJS) for other libraries to maintain a consistent api across all of them. That way, if another library is already included, I just include the adapter. I'm basing the api heavily on MooTools since it's so awesome.
