It's a bit speculative, but here is my shot at it.
Functional langage tend to put the emphasis on a declarative syntax. It tend to read like statement of a fact rather than like commands. Example
var eligible = customers.where(c => c.age > 30);
which can be read as "the eligible customer are the customers whose age are over 30". By constrast, the imperative language read like a sequence of command
for (customer in customers)
if (customer.age > 30)
That can be read as "Check each customer, and if their age is over 30, add them to the eligible collection"
Adding a a
set and a
get operation would make jQuery feel like an imperative library. You can constrast the way to read the following statements
// The element tag have an html of <p>hello</p>
// content represent the html of the element tag
var content = $("#element").html();
// Set the element tag to an inner html of <p>hello</p>
//Get the html of #element, and put it in the content variable
var content = $("#element").getHtml();
By keeping actions verb out of the jQuery api, they made it feel like a declarative API. It give a consistent, functional feel to the library. That is why I think they overloaded the keywords.