Next to jQuery, Underscore is my most-used JS library. Makes scripting client-side behavior so much more pleasant.
-----
http://documentcloud.github.com/underscore/test/test.html
In general, Underscore is intended for logic and data manipulation, and jQuery handles the DOM and Ajax calls.
Why does Underscore.js get the order of arguments wrong? There’s a reason why it’s map(fn, l), not map(l, fn). And the reason is currying.
I find that very annoying for the kind of functional programming I tend to do. For that reason alone I started looking at Wu.js instead.
Am I missing something?
However, having higher-order functions in JavaScript take their function argument in the final position is an extremely common and important pattern in JavaScript. Most libraries prefer this:
call(arg, arg, function() {
...
});
call(function() {
...
}, arg, arg);I have a feeling that either the authors of Underscore don't fully get functional programming, or I don't. Of course, the latter is much more likely, that's why I'm looking for someone to set me straight.
Depending on your definition, nothing in JavaScript is "fully functional programming", because then it would have to be side-effect-free, and JavaScript is very much not that language.
Calling them "functional helpers" is mostly a way of distinguishing the style in which you use them, as opposed to the object-oriented versions of the same helper functions, which can be found in libraries like Prototype.js. The idea here being that you can use them in a functional style without having to extend native objects.
As I mentioned above, calling "map" with the iterator as the final argument isn't a limitation here -- it's a feature. There aren't many (any) situations I've ever seen in real-world JS where you'd want to curry together a list of iterators, and then map them together across the array, all at once. And if you do want to do such a thing, you can accomplish it either like this:
_.map(list, function(item) {
return convert1(convert2(convert3(item)));
});
http://documentcloud.github.com/underscore/#compose
_.map(list, _.compose(convert1, convert2, convert3));And in javascript, having the function last is relatively standard and much nicer to look at.
-----
var sum = curry(reduce, add);
Am I wrong in thinking that this kind of currying is one of the fundamental building blocks of functional programming?
var sum = function (a) {
return _(a).reduce(function (m, n) {
return m + n;
}, 0);
};
sum([1,2,3,4,5,6,7,8,9]); // => 45
var add = function (m, n) {
return m + n;
},
partial = function (mth, fn) {
return function (l) { return _(l)[mth](fn, 0); };
},
sum = partial('reduce', add);
sum([1,2,3,4,5,6,7,8,9]); // => 45