I Need jQuery

No, you don't. You can find it useful, and that's fine. It makes you feel more comfortable with front-end coding. Another perfectly valid reason.

But you don't need jQuery.

Also, looking at your examples, I find that maybe jQuery has prevented you to consider some recent but common new features in browsers. For example:

In native, You can't set multiple styles to element at once.

Sure you can. Consider this:

Object.assign(element.style, {
  'background-color': '#000000',
  'color': '#ffffff'
});

More than that, you must be aware of what jQuery does for every operation. It creates a collection, attaches its methods, bindings and callbacks. It performs its checks. It has a cost. And everyone should be aware of that.

That's why it's wrong to compare .hide() to simply setting .style.display = 'none': in fact, the former does much more than the latter, and should generally be avoided.

In native, element getter methods has too many kinds and has too long name.

This is a non-issue, as you can use a plethora of tools that help you writing your code with intellisense and the like.

Anyway, performing DOM operations should be hardly be an issue nowadays. You should concentrate on the structure of your application, and jQuery doesn't help in that sense.

All in all, we still have to deal with legacy code that has to maintained, and jQuery is ubiquitous there. So, should I know jQuery? Absolutely. Should I start a project using jQuery? If it's not just a simple landing page, no.

53

Come on, it's not realistic to load a big library just because DOM API is "too long". Create some helpers if you care about the character counts.

Regarding, querying API has "too many kinds", all other queries are possible by just using querySelectorAll.

13

I still think it would be better to use JS. You are not taking in consideration the code behind $.

Also you can use querySelector or querySelectorAll to select you tags, ids and classes, hence you don't need document. getElement...

For styles

// Set multiple styles in a single statement
elt.style.cssText = "color: blue; border: 1px solid black"; 
// Or
elt.setAttribute("style", "color:red; border: 1px solid blue;");

No need to set one style at a time.

Adding html strings, I like this way:

var div = document.createElement('div');
div.innerHTML = '<p>blah</p>';

Toggle

.classList.toggle('className');

Most importantly, you learn js and don't load more code then you need

12

The controversy in the comments makes me laugh anytime someone thinks jQuery is dead. Of course there's specialized stuff that makes some of these things easier in some instances, and as JS evolves, it adds some of this, but it's not dead, and doesn't need to be.

Thanks for keeping this alive, because sometimes you don't need a whole framework to to the little things, and sometimes there's so much specialization that no one framework will cover it well.

Anyone who gets cranky about a tech. that other people are using is either posturing or doesn't know the whole story about an individual project. There's a lot of legacy stuff out there, including browsers that sometimes have to be targeted -- better than it used to be, but still an issue.

Yes, jQuery is getting slowly replaced, but there's no reason to stop showing people how to do the basics until they can pop a framework (sometimes you don't know the best one to use in a given instance) in or upgrade their legacy stuff. Sometimes you just need to know what the previous people did so you CAN replace it with newer ES versions or framework code. Sometimes you need to get it past an entrenched IT team that has whitelisted jQuery libs but not necessarily approve of the latest and greatest yet.

For those laughing at the last bit, or refusing that kind of work, I'm happy to collect your paycheck once I'm done with my stints doing data integration work that you're also refusing.

8

There are other advantages like jQuery caches the selectors.

You can also import only jQuery small functions and use those.

Ppl say we don't need jQuery anymore because we moved to webComponents, to use jQuery there is like playing God and is not good to overwrite the internal state of a comp from outside, aka react, vuejs.

I would still use jQuery for small static websites like landing pages or if I want to make a quick solution.

2

If you really do such low-end stuff exclusively, you should really be able to do it without the whole of jQuery. On the other hand, if you want to do more advanced front-ends, you should definitely go without jQuery and let a framework like preact or Vue manage the DOM for you.

Also, you should not use style or shorthands like .hide() unless there's no other option. Better set class names (like .hidden, [hidden]) and handle them in CSS.

3

Hi, in case. Here is some helpers functions:

// Select Element by ID
const selectIdElement = (element) => {
return document.querySelector(element);
};

// Select Element by class, id or tag name
const selectXElement = (element) => {
return document.querySelector(element);
};

// Select All Element That have the same attribute
const selectAll = (element) => {
return document.querySelectorAll(element);
}

// Select the parentNode
const selectParent = (element) => {
return document.querySelector(element).parentNode;
}

// Select the ChildNode
const selectChild = (element) => {
return document.querySelector(element).children;
}

// Create HTML element
const createElement = (element) => {
return document.createElement(element);
}

// Create text node
const createTxtNode = (element) => {
return document.createTextNode(element);
}

// Append Element to the DOM
const appendElement = (parentElement, childElement) => {
return parentElement.appendChild(childElement);
}

2

Some notes:

In native JS you can add several css styles to element:

div.style.cssText="color: red !important; \
    background-color: yellow; \
    width: 100px; \
    text-align: center; \
    blabla: 5; \
  ";

But you have some restriction: style.cssText overrides previous properties style

1

Btw some native styling hint if you have modern browsers at hand - the following is possible:

Object.assign(element.style, {
  color: 'red',
  fontSize: '24px',
  // and so on
})

3

Well, I think jquery Is still a valid option when you just want to make a simple website, which makes for 99% of the websites out there. There's no need to go react or vue if you're not really gonna be building an app-like kind of thing.

JQuery gets too much undeserved hate lately, because some people that got a sort of addiction to it and can't code 3 lines of JavaScript without it.

Sure, it was much more relevant in the dark ages of CSS 2 and crappy js, but even today, it's a valid tool for some works.

The key is to know when and why use each tool. (Which btw, the post makes an awful job at)
If all you got is a hammer, all tasks will look like nails.
Sometimes vanilla js will do, sometimes you need to go with a modern framework like vue or react, and sometimes the good ol' jquery will work just fine. Heck, nowadays most of what we used jquery for back in the day can now be achieved with CSS 3 and the simplest event listeners

I might not use it anymore , but I refuse to speak badly of a tool that provided us with such a great experience in the past. Which also means we might have to maintain legacy jquery code for a long, long time.

1

This is just terrifying on soo soo many levels. Next we going to have developers saying they need bootstrap to colour buttons

3

A Javascript developer needs jQuery like a fish needs a bicycle.

...I'm actually unsure if I believe this myself. I just REALLY wanted to write it.

3

Here is a list, jQuery to JS plainjs.com/javascript/

1

zamjs.com

No more long sentences from DOMapi

1

I've added about the area of ​​this post.

2

I like how people grow up learning js with jquery say shit like dom operation cost and don’t use hide method.

1

$ = q => [... document.querySelectorAll(q)]

2

Jquery still rocks even in 2018

1

jquery syntax is still useful for web scrapping i think.

1

So. If you are just lazy you need to use jQuery.

1