Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I googled quite a lot looking for the answer to this question but didn’t find anything.
Aside of additionnal functionalities offered by a script loader like yepnope, is it going to give me better performance and better cache management than jQuery.getScript?
Thanks in advance,
Simon
In principle, their functionally the same. The biggest gain you get from something like yepnope is integrated conditional loading. Whereas, with $.getScript, you’d have to do any requisite boolean checks manually. There’s also little things like the fact that yepnope is already supported by tests, whereas if you wanted the same certainty in your custom conditional-loading code, you’d have to write your own.
In short, yepnope is just a time-saver like jQuery itself is a time-saver. There’s nothing you can do in jQuery that you can’t do in vanilla JavaScript; it just takes more time, energy, and effort. If you’re thinking about dynamically loading scripts, I would recommend that you use a library for that, instead of re-inventing the wheel.
Interestingly, yepnope is actually bundled into Modernizr (I didn’t know that). So, if you’re looking to start getting into HTML5, you can include Modernizr and get your shivs, feature-sensing sugar, and dynamic script loading all in one.