jQuery Forum

I got a 'Malicious Cookie' warning when browsing above link...

It's faster still to simply cache jQuery objects in variables in your code as recommended.

Not sure what the point is of adding an extra layer of code. It certainly doesn't add to readability. Why not just add appropriately-named variables to your code to hold often-used objects?

Simply because, when calling multiple times the same variables in successive call of the same method, UtilDom warrants retrieving things from cache. It is a kind of references singleton class.

Here a link to explanation of updates I made for a projet running ios6 (iphone 4)  http://forum.jquery.com/topic/jquery-mobile-phonegap-slow-choppy

You're totally missing the point made by watusiware.  If you want to cache references to an element, then use a simple variable for frequently accessed objects instead of inventing an extra unnecessary caching layer.  jQuery Mobile loads documents into the DOM via AJAX and you don't need an extra caching layer just to access elements in an efficient manner.

This:
UtilDom.get("your-selector").doSomething();
UtilDom.get("your-selector").doSomething();
UtilDom.get("your-selector").doSomething();

is not more efficient either from a memory perspective or a speed perspective than just using plain old variables as they were intended to be used:

var target = $("your-selector");
target.doSomething();
target.doSomething();
target.doSomething();

All you're doing is adding an extra layer that doesn't provide any more value than if you used variables correctly to begin with.

Except that UtilDom garantees the same reference in the whole application...

Thibaut de Sany (Transhumanist)
http://thibaut.desany.eu

Except that UtilDom garantees the same reference in the whole application...

Not sure what your point is.  So can standard variables...  UtilDom is really just an object array variable with additional lookup overhead on top of it.  So, instead of just storing the item once in a variable and reusing it directly, one has to go through the extra logic of UtilDom.get() every time to check to see if the reference already exists.  I'd rather just look up the element once, store it in a variable, and reuse it directly every time I need it than call a function that adds additional logic to check to see if the reference already exists in an array.

Based on your response I'm not sure you truly understand how references can be cached using regular ol' variables instead of adding the overhead of yet another library/utility.  I'll use the basic capabilities of the core language over an unnecessary library any day...  That's guaranteed to be faster.

Hello Ayan,