> Should keep it simple. changing .load to .ajaxLoad is > even unneccessary.
None of this is absolutely necessary. jQuery works as-is, and the changes may break existing code, so the easiest path is to leave everything alone. The issue is whether we can make changes to the jQuery API that make it more consistent, intuitive, and easier to learn. Changes to accomplish that will probably remove things from the core or change names, but as long as there is a plugin for migration I don't see a problem with that. The other issue is that jQuery can't stay light and continue to accumulate functionality in its core. A year from now I would be sad if jQuery core had bulked up to the size of prototype or some of the other frameworks. Losing weight is never easy. The whole idea of the plugin architecture is to let people add the functionality they need and leave out the stuff they don't use. Some of the stuff in the core may not deserve to be there, but it can certainly live on inside a plugin. _______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
