John: > That's not happening. That will change a critical method of the > jQuery API - breaking thousands of jQuery sites.
True. Flat out removing .remove() would be stupid and disastrous. Gavin: > Deprecation and aliasing is a quick path to API bloat, IMO. Agreed, it's a slippery slope... but I'd argue that .get() and .remove() are really the only two methods in the current API that need it. The .get() -> .toArray() deprecation +aliasing has already been put on the roadmap, so doing the same for .remove() wouldn't be too much of an addition. The number of developers using jQuery is growing tremendously, and jQuery will most likely remain in use for years to come, so IMO there's a huge gain to be had in polishing a few edges here and there, now rather than later. Anyway, just food for thought. -- Már --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
