3 ms·

querySelectorAll is great, assuming you know your users aren't using IE 6 / 7. Cross browser support is really where jQuery shines. jQuery is starting to becom

• jbri 13y ago
  Why not use a polyfill to get the same functionality on older browsers? That also gives you the benefits of better performance on browsers that do support the native version.
  • ckuijjer 13y ago
    jQuery uses getElementsByID, getElementsByClassName etc. when available in the browser. There is only a small overhead in parsing the selector to see if it's e.g. a simple ID or class selector.
    • octatone2 13y ago
      Or should create a DOM element. I think the main pitfall of $() is that it tries to be too many things at once. Node creation and selection should be two separate slimmed down functions. There's no need (other than convenience) for selection and creation exist in the same function.
      • kibibu 13y ago
        And onDocumentReady handling :) You can do this: $(function() { /* handle onDocLoad */ })
        • octatone2 13y ago
          Exactly, there's too many if this than do thats in $().