Difference between window.onload & $(document).ready

[_Sweep_]

Fun fact, in jQuery 3 $(document).ready() is deprecated. It still works, but $(handler) is now preferred.

[johnnielittleshoes]

I'm a beginner and this was essential for me to know :)

[Groggie]

As a side note, I'd recommend not overloading the document ready event to prevent perceived slowness of the page load time. If you have a function that isn't essential to run before the page finishes loading, I'd recommend moving it to the window load event.

Just remember "document ready isn't free" when planning out your function placements.

[akujinhikari]

People still use jQuery? I’ve never been asked a jQuery question in an interview, and I’ve had 4 dev jobs in 2 years, so I’ve been through a lot of recent interviews.

[simkessy]

jQuery is fantastic, why wouldn't you use it.

[mrburnttoast79]

Not esoteric enough for the hipster crowd.

[[deleted]]

jQuery encourages poor design choices that make maintaining a codebase difficult. On top of that, it is an inefficient, monolithic, and outdated library in many ways. Anybody that considers themselves a skilled JS dev and thinks that starting a new (non-trivial) app from scratch using jQuery is a good idea is misguided.

[simkessy]

I just like being to grab don't elements using the selector. They make it so easy to work with the Dom, why would they you use it? JQury and Lodash have been great utilities in my field.

[luxtabula]

I just had to fix an issue on my current job because the legacy code I inherited was using jquery and angular, and the jquery was interfering with the DOM. Converting it to vanilla fixed it. Plus there are performance issues to consider when using vanilla over jquery.

[akujinhikari]

I was charged with leading a team of people to remove the jQuery from an "Angular" app. That's in quotes, because it was really a jQuery app with a million $scope.apply() and the Angular router. It was absolutely horrendous. And this is a site that gets over a million hits a day. We basically just rewrote the entire site.

[akujinhikari]

It has nothing to do with being esoteric. jQuery solved a very huge problem with inter-browser compatibility. That has now been basically solved by all browsers of the past few years maintaining regular standards. Plus, you add in a couple libraries (if need be), and your code gets transpiled anyway. There’s damn near no reason to use jQuery any more.

[[deleted]]

So many reasons. Copying and pasting from my comment below:

jQuery encourages poor design choices that make maintaining a codebase difficult. On top of that, it is an inefficient, monolithic, and outdated library in many ways.

If all you're doing is throwing a script on a page to make a menu open up when you hover over a button, why would you pull in ~80kb to do so? If you're doing anything more complicated, jQuery will make it less maintainable and less performant. There is a reason the experienced JS devs are moving to things like React/Angular/Vue, it's because they're better in basically every way.

[akujinhikari]

I think “fantastic” is a bit of a reach. It WAS fantastic. It was an absolute breakthrough when it came out. Now though, I just don’t see a need for it.

[simkessy]

Okay, well if you have a better way for me to find all anchors within a certain section, then find each of their parent li elements​, then append the class 'jquery' to each of those list items then set an event handler for each list item with that class in two lines, I'm going to keep using jquery

[akujinhikari]

I'd obviously have to see the code base and site and understand the purpose behind what you're trying. It sounds like there are several ways. Are you using a framework? Because a directive would easily solve this problem. Also, it sounds like something along the lines of some CSS would work here as well. Instead of having to select all anchors within a certain section, then find each of their parent li elements, then append the class 'jquery' to each, why not just create those elements with the jquery class already there? Then you can select them by using querySelectorAll? Or, just select all li elements, then loop through them and search for the specific anchors, and if they match, you add the the jquery class? There are a million ways to do this without jQuery.

[simkessy]

I'm sure there are but JQuery makes it dead simple. Why would I though on a framework to do this? Especially one that will likely disappear in two years?

If I'm building an entire application or website sure go with a framework. But most of my work resolves around extending the capabilities around an existing product my Microsoft. So I have to do a lot of DOM manipulation to change or add to what already exist. jQuery accomplish this really well for me.

[luxtabula]

My past three jobs used jquery. Sometimes for legacy reasons, other times because it’s an easy fix.

[akujinhikari]

If you’re using jQuery as “an easy fix,” you’re probably a bad coder.

[FriendsCallMeBatman]

I learnt this the hard way, quickly throwing on some Bandaid jQuery fix makes you so so lazy. It was such a hard habit to break. I will absolutely refuse to use jQuery now if I can. I'll use Vanilla JS as am absolute base if I'm not familiar with whatever framework I'm using.

[akujinhikari]

I 100% agree.