3 ms·
No jQuery actually means: 1. Less dependencies for your JavaScripts 2. Less "magic" behind the scenes 3. Native JS-engine optimisation 4. Switch of though-p
by drinchev 10y ago
No jQuery actually means:
1. Less dependencies for your JavaScripts
2. Less "magic" behind the scenes
3. Native JS-engine optimisation
4. Switch of though-process ( jQuery, although quite flexible ), makes you think that everything is "string", "array", "object" and sometimes you need the bare Node-element e.g. https://developer.mozilla.org/en-US/docs/Web/API/Element https://developer.mozilla.org/en-US/docs/Web/API/Element