jQuery 4.1.0

jQuery 4.1.0’s release prompts a reassessment of the library’s role now that modern JavaScript, CSS, and frameworks like React have absorbed many of its original advantages. Commenters note that jQuery still powers a majority of websites—largely via legacy systems and platforms like WordPress—and praise its fluent, concise API and cross‑browser abstractions, even as they acknowledge it’s no longer ideal for building complex UIs. Many see it as a historically pivotal tool that remains practical for incremental enhancement and maintaining older codebases, while newer projects increasingly favor vanilla JS or lighter modern alternatives.

Ongoing maintenance and jQuery UI

  • jQuery 4.1.0 is noted as a 2026 release; 3.8.0 is mentioned as a “send‑off” for older browsers per the linked blog.
  • jQuery UI is in maintenance mode with limited updates; its version lags (1.14) and it’s a separate project from core jQuery.
  • Some miss jQuery UI, others recall it as lower quality than core jQuery and bogged down in rewrites.

Prevalence and legacy usage

  • Multiple comments say a large share of the web still uses jQuery, with figures cited around 53–64% of sites; sources differ.
  • Examples mentioned: Microsoft, Pinterest, Adobe, Yahoo, WordPress, Samsung, Archive.org, cPanel, StackOverflow.
  • WordPress bundling is seen as a major driver of its long tail.

Use in new projects

  • Some still choose jQuery for small, non‑SPA sites, especially among backend‑leaning developers and “framework‑averse” people.
  • Others avoid it on new work, preferring vanilla JS, HTMX, Alpine, Datastar, hyperscript, or modern frameworks.
  • A common pattern: keep using it when branching from older projects rather than refactoring away.

jQuery vs vanilla JS and modern APIs

  • Many argue that modern DOM APIs (querySelector, classList, fetch, promises) and CSS (Grid/Flexbox) have replaced most of jQuery’s original reasons to exist.
  • Counter‑argument: jQuery remains less verbose, with powerful collections and chaining, and avoids repetitive null checks.
  • Some dislike jQuery’s behavior of silently no‑oping on empty selections, seeing it as hiding bugs.

API design and ergonomics

  • jQuery’s fluent, chainable API is widely praised as elegant and influential.
  • Its “do everything on a collection” model is seen as a big productivity and readability win versus NodeList and inconsistent JS collection APIs.
  • The event system—allowing custom events on arbitrary objects—is highlighted as a still‑useful pattern.

Browser support, performance, and payload

  • jQuery 3.x continues to support very old browsers (including IE9–11 and legacy mobile), which some consider still necessary in certain enterprises or poorer regions.
  • Others argue such support should be dropped and replaced with targeted polyfills.
  • File size is debated: some see ~25–27 kB compressed as negligible; others report noticeable gains on low‑bandwidth devices after removing jQuery.

AI and migration

  • Several note that modern LLMs make it easy to port 10+ year‑old jQuery apps to vanilla JS/TS.
  • This reduces the need for jQuery in new code but reinforces its importance in legacy maintenance and incremental rewrites.

Sentiment and nostalgia

  • Many express strong affection and gratitude for jQuery’s role in taming cross‑browser chaos (especially IE6/7 era).
  • Others see it as largely obsolete for complex UIs compared to component‑based, reactive frameworks, while still respecting its historical impact.