Correct me if I'm wrong, but I thought .get, .post, .getJSON, .getScript, and .load were only shortcuts and simplified versions that wrap the more complex functionalities of .ajax().

If you want to have a cache option, then you should probably use $.ajax(options), and set the cache setting accordingly. It's not that hard to master and it does a lot more than the simplified versions...

i.e.:

var data = {param1:"value1",param2:"value2"};
var options = {
 data: data,
 url: "ajax.php",
 dataType: "script",
 cache: false,
 type: "GET"
 success: function(r){
  // DO SOMETHING ELSE HERE IF NEEDED
 }
}

$.ajax(options);

This will have the same effect as if you were using $.getScript() but you have some extra control.

You are right, but this will make code less readable.

Ease of use is an important reason too.

My guess is that why getScript function is present in jQuery.

Why not code like this:

$.getScript("http://domain.com/script.js", {cache: true});

or

$.getScript("http://domain.com/script.js", true);

I think that .getScript is the only exception out of other .ajax wrappers to have cache control.

The attached patch adds an options parameter to jQuery.get() and jQuery.post(), which is merged in with the defaults. This allows us to add an options parameter to the getScript() function, so we could essentially pass in {cache:true}, and it would merge it into the jQuery.ajax() call.

http://dev.jquery.com/attachment/ticket/3004/getpostoptions.patch

This looks like it's going to be a wontfix. Marking for further review.

Updating to low priority

This is trivially easy to do by appending a random number to the url, or use $.ajax. $.getScript is meant to be simple and these changes would just complicate it.