This is digressing into a meta-discussion about API design.
Complex APIs are difficult to document, hard to remember, and often have conflicting or non-intuitive results. For an example, see the 33 different options for
$.ajax(), the 3 completely different semantics for
$().toggle() or the 9 different signatures for
$(). Try to figure out whether
$(elem).load(x) will load content via AJAX or set an onload handler without knowing the data type of
x. Go see what happened when we made
.outerWidth() a setter in 1.8.
jQuery was meant to be easily extended by users so they can use it in a way that works for them. We should not be creating a complex API that reflects the union of all thoughts about how to use jQuery in all situations.