5 ms·
You don't need jQuery. Every problem jQuery solved has been standardized into native javascript so you can just use Javascript to build web apps. For example i
by cocktailpeanuts 6y ago
You don't need jQuery. Every problem jQuery solved has been standardized into native javascript so you can just use Javascript to build web apps.
For example instead of $(".button"), you can do document.querySelector(".button"), and so on.
That said, if you must use a framework and looking for something less complicated than react, look into Vue or Svelte.
- meesterdude 6y ago> Every problem jQuery solved has been standardized into native javascript Some problems, sure. Every problem? I think that's a stretch. Jquery still has it's applicability and can in some cases lead to simpler code.
- cocktailpeanuts 6y agoLike what? The main purpose of jQuery was to have a unified API for dealing with the issue of every browser having their own quirky implementation of the web standard. All of those are gone today and we now have a pretty much standardized Javascript that you can write once and run in any browser.
- jraph 6y agoI never used jQuery, but it seems that two other problems that is solved and that current browsers largely cover now are: - easier AJAX requests (fetch does this) - selecting nodes using CSS-like selectors (querySelector / querySelectorAll) Hiding elements too: HTML now has the hidden attribute. Maybe manipulating HTML/CSS classes? (classList has everything)
- 1123581321 6y agoThat does not solve the problem because jQuery spaghetti comes from developing features. Equivalent native commands must accumulate the same increasing complexity.