Unless your DOM tree is huge and you're trying to select something
massive in one go, the performance difference between a simple jQuery
ID selector (e.g. $("#myID")) vs. a native getElementById selector
should be very negligible, because jQuery uses that same native
selector.
You should demonstrate to us a page that you have that seems to be
slower. Perhaps your issue doesn't lie in the actual ID selector, but
how you implemented other jQuery code vs. what you had before.
On Oct 14, 12:15 pm, JenniferWalters <jenniferwalt...@email.com>
wrote:
> I don't have a specific code snippet that is a problem. I just
> started using jQuery instead of DOM because everyone speaks of it. I
> do qutie a bit of Setup stuff at the start of web pages, and I have
> noticed a tremendous difference in the time a user can begin actually
> working in the web page when using $('xxxx') versus the DOM. And this
> isn't fractional, some of it is 50% or more longer for Load Time and I
> have had to backtrack and redo some things with DOM instead.
>
> But I must say, it is great because of all the addins\plugins that
> everyone has written for it. I wish the quality and quantity of these
> freeware addins were available in other languages.
>
> Have I concluded the following correctly? Use the jQuery quality
> addins that enhance my applications (and that I am incapable of
> enhancing like these gifted authors). BUT use jQuery within my
> application sparingly (use DOM instead) because of the slowness.
>
> On Oct 14, 5:27 pm, Matt Kruse <m...@thekrusefamily.com> wrote:
>
> > On Oct 14, 3:33 pm, JenniferWalters <jenniferwalt...@email.com> wrote:
> > If you provide a simplified example case that you think is overly
> > slow, perhaps someone can identify other issues contributing to the
> > performance problem.
>
>
