4 ms·

Fisrt include jQuery as a whole into the base standard. That would help a lot.

• edoceo 1y ago
  I <3 jQuery but, no.
  • lofaszvanitt 1y ago
    What no? Why can't we have nice things, like concise, easy to remember, not overly elaborate syntax?
    • ameliaquining 1y ago
      jQuery is large and contains a lot of things. Which specific features do you think the DOM needs?
      • lofaszvanitt 1y ago
        What do you think is alrite in the current spec?
      • eszed 1y ago
        From bevr1337's comment, above: > its API was a reflection of the domain. As a developer, I want to query for a node (CSS selector, xpath, etc.) to affect change and traverse to other nodes That's what I miss about it.
        • jraph 1y ago
          Doesn't querySelector(All) provide this?
          • troupo 1y ago
            Not entirely. There's a reason people do Array.from(querySelectorAll) to do more than just `forEach`
            • jraph 1y ago
              So you are saying that Array.from(querySelectorAll) gets you there? What are you missing then? Genuinely asking, I have no clue what's being alluded to without being clearly mentioned in this thread.
              • troupo 1y ago
                > So you are saying that Array.from(querySelectorAll) gets you there? What are you missing then? Array.from adds friction. The need to wrap querySelector in null checks adds friction. The fact that they are not composable in any way, shape, or form, with any DOM methods (and that DOM methods are not composable) adds friction. jQuery was the fore-runner of fluid interface design. Nothing in the DOM before, then, or since ever thought about it. Even the new APIs are all the same 90s Java-style method calls with awkward conversions and workarounds to do anything useful. That's why sites like "You don't need jQuery" read like bad parody: https://youmightnotneedjquery.com https://youmightnotneedjquery.com E.g. what happens when it's not just one element? $(el).addClass(className); // vs. el.classList.add(className); Or: why doesn't NodeList expose an array-like object, but provides an extremely anaemic interface that you always need to convert to array? [1] $(selector).filter(filterFn); // vs. [...document.querySelectorAll(selector)].filter(filterFn); There's a reason most people avoid DOM APIs like the plague. --- [1] This is the entirety of methods exposed on NodeList https://developer.mozilla.org/en-US/docs/Web/API/NodeList https://developer.mozilla.org/en-US/docs/Web/API/NodeList Instance properties - length Instance methods - entries() // returns an iterator - forEach() - item() - keys() - values()
                • jraph 1y ago
                  I agree that DOM lists not being real arrays is a pita. I can understand why for getElementBy* methods which return live lists, but it's less clear for those methods returning fixed lists. But to me, these are minor inconveniences and habits. A thin wrapper can get you there easily if you care enough. I personally dislike this array/element confusion that jQuery adds.
• bravesoul2 1y ago
  Out of FE for a whole but isn't that done to a great extent.
  • lofaszvanitt 1y ago
    done, how?
    • bravesoul2 1y ago
      https://developer.mozilla.org/en-US/docs/Web/API/Element/querySelector https://developer.mozilla.org/en-US/docs/Web/API/Element/que...