@John I agree - in standard usage of jQuery is rare to use get(). Anyway this is not always true inside plugins and jQuery source. toArray() is not only an aesthetic improvement, but also great optimization because of direct use of native Array.prototype.slice.
On Jan 27, 12:11 am, John Resig <[email protected]> wrote: > Robert - > > Well, getting a jQuery set as an array is a pretty rare step to begin > with - almost always it is because jQuery should be used in another > way. > > --John > > On Mon, Jan 26, 2009 at 3:02 PM, Robert Katić <[email protected]> wrote: > > > @Már > > The reason of posting here, is because, in my opinion, the get() makes > > code less readable. > > If an considerable number of developers think the same, maybe it is > > time to resolve this in jQuery directly, because it is better then > > encourage developers to create own dialects (bunch of aliases). > > > On Jan 26, 11:44 pm, Már Örlygsson <[email protected]> wrote: > >> Robert: while I agree with you that the whole .get() thing has always > >> seemed kind of weird, it's now part of jQuery history and cannot be > >> easily changed. > > >> If it bugs you, just write your own alias: > > >> jQuery.fn.toArray = jQuery.fn.get; > > >> ...and make sure to always access single element with > > >> collection[index]; > > >> rather than > > >> collection.get(index); > > >> And you'll never notice the difference. > > >> -- > >> Már Örlygsson > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
