Differences between lodash and underscore [closed]

Differences between lodash and underscore [closed]

Why would someone prefer either the lodash.js or underscore.js utility library over the other?
Lodash seems to be a drop-in replacement for underscore, the latter having been around longer.
I think both are brilliant, but I do not know enough about how they work to make an educated comparison, and I would like to know more about the differences.

Solutions/Answers:

Solution 1:

I created Lo-Dash to provide more consistent cross-environment iteration support for arrays, strings, objects, and arguments objects1. It has since become a superset of Underscore, providing more consistent API behavior, more features (like AMD support, deep clone, and deep merge), more thorough documentation and unit tests (tests which run in Node, Ringo, Rhino, Narwhal, PhantomJS, and browsers), better overall performance and optimizations for large arrays/object iteration, and more flexibility with custom builds and template pre-compilation utilities.

Because Lo-Dash is updated more frequently than Underscore, a lodash underscore build is provided to ensure compatibility with the latest stable version of Underscore.

At one point I was even given push access to Underscore, in part because Lo-Dash is responsible for raising more than 30 issues; landing bug fixes, new features, & perf gains in Underscore v1.4.x+.

In addition there are at least 3 Backbone boilerplates that include Lo-Dash by default and Lo-Dash is now mentioned in Backbone’s official documentation.

Check out Kit Cambridge’s post, Say “Hello” to Lo-Dash, for a deeper breakdown on the differences between Lo-Dash and Underscore.

Footnotes:

  1. Underscore has inconsistent support for arrays, strings, objects, and arguments objects. In newer browsers, Underscore methods ignore holes in arrays, “Objects” methods iterate arguments objects, strings are treated as array-like, and methods correctly iterate functions (ignoring their “prototype” property) and objects (iterating shadowed properties like “toString” and “valueOf”), while in older browsers they will not. Also, Underscore methods like _.clone preserve holes in arrays, while others like _.flatten don’t.

Solution 2:

Lo-Dash is inspired by underscore, but nowadays is superior solution. You can make your custom builds, have a higher performance, support AMD and have great extra features. Check this Lo-Dash vs Underscore benchmarks on jsperf and.. this awesome post about lo-dash:

One of the most useful feature when you work with collections, is the shorthand syntax:

var characters = [
  { 'name': 'barney', 'age': 36, 'blocked': false },
  { 'name': 'fred',   'age': 40, 'blocked': true }
];

// using "_.filter" callback shorthand
_.filter(characters, { 'age': 36 });

// using underscore
_.filter(characters, function(character) { return character.age === 36; } );

// → [{ 'name': 'barney', 'age': 36, 'blocked': false }]

(taken from lodash docs)

Solution 3:

If like me you were expecting a list of usage differences between underscore and lodash, there’s a guide for migrating from underscore to lodash.

Here’s the current state of it for posterity:

  • Underscore _.any is Lodash _.some
  • Underscore _.all is Lodash _.every
  • Underscore _.compose is Lodash _.flowRight
  • Underscore _.contains is Lodash _.includes
  • Underscore _.each doesn’t allow exiting by returning false
  • Underscore _.findWhere is Lodash _.find
  • Underscore _.flatten is deep by default while Lodash is shallow
  • Underscore _.groupBy supports an iteratee that is passed the parameters (value, index, originalArray),
    while in Lodash, the iteratee for _.groupBy is only passed a single parameter: (value).
  • Underscore _.indexOf with 3rd parameter undefined is Lodash _.indexOf
  • Underscore _.indexOf with 3rd parameter true is Lodash _.sortedIndexOf
  • Underscore _.indexBy is Lodash _.keyBy
  • Underscore _.invoke is Lodash _.invokeMap
  • Underscore _.mapObject is Lodash _.mapValues
  • Underscore _.max combines Lodash _.max & _.maxBy
  • Underscore _.min combines Lodash _.min & _.minBy
  • Underscore _.sample combines Lodash _.sample & _.sampleSize
  • Underscore _.object combines Lodash _.fromPairs and _.zipObject
  • Underscore _.omit by a predicate is Lodash _.omitBy
  • Underscore _.pairs is Lodash _.toPairs
  • Underscore _.pick by a predicate is Lodash _.pickBy
  • Underscore _.pluck is Lodash _.map
  • Underscore _.sortedIndex combines Lodash _.sortedIndex & _.sortedIndexOf
  • Underscore _.uniq by an iteratee is Lodash _.uniqBy
  • Underscore _.where is Lodash _.filter
  • Underscore _.isFinite doesn’t align with Number.isFinite
    (e.g. _.isFinite('1') returns true in Underscore but false in Lodash)
  • Underscore _.matches shorthand doesn’t support deep comparisons
    (e.g. _.filter(objects, { 'a': { 'b': 'c' } }))
  • Underscore ≥ 1.7 & Lodash _.template syntax is
    _.template(string, option)(data)
  • Lodash _.memoize caches are Map like objects
  • Lodash doesn’t support a context argument for many methods in favor of _.bind
  • Lodash supports implicit chaining, lazy chaining, & shortcut fusion
  • Lodash split its overloaded _.head, _.last, _.rest, & _.initial out into
    _.take, _.takeRight, _.drop, & _.dropRight
    (i.e. _.head(array, 2) in Underscore is _.take(array, 2) in Lodash)

Solution 4:

In addition to John’s answer, and reading up on lodash (which I had hitherto regarded as a “me-too” to underscore), and seeing the performance tests, reading the source-code, and blog posts, the few points which make lodash much superior to underscore are these:

  1. It’s not about the speed, as it is about consistency of speed (?)

    If you look into underscore’s source-code, you’ll see in the first few lines that underscore falls-back on the native implementations of many functions. Although in an ideal world, this would have been a better approach, if you look at some of the perf links given in these slides, it is not hard to draw the conclusion that the quality of those ‘native implementations’ vary a lot browser-to-browser. Firefox is damn fast in some of the functions, and in some Chrome dominates. (I imagine there would be some scenarios where IE would dominate too). I believe that it’s better to prefer a code whose performance is more consistent across browsers.

    Do read the blog post earlier, and instead of believing it for its sake, judge for yourself by running the benchmarks. I am stunned right now, seeing a lodash performing 100-150% faster than underscore in even simple, native functions such as Array.every in Chrome!

  2. The extras in lodash are also quite useful.

  3. As for Xananax’s highly upvoted comment suggesting contribution to underscore’s code: It’s always better to have GOOD competition, not only does it keep innovation going, but also drives you to keep yourself (or your library) in good shape.

Here is a list of differences between lodash, and it’s underscore-build is a drop-in replacement for your underscore projects.

Solution 5:

This is 2014 and a couple of years too late. Still I think my point holds:

IMHO this discussion got blown out of proportion quite a bit. Quoting the aforementioned blog post:

Most JavaScript utility libraries, such as Underscore, Valentine, and
wu, rely on the “native-first dual approach.” This approach prefers
native implementations, falling back to vanilla JavaScript only if the
native equivalent is not supported. But jsPerf revealed an interesting
trend: the most efficient way to iterate over an array or array-like
collection is to avoid the native implementations entirely, opting for
simple loops instead.

As if “simple loops” and “vanilla Javascript” are more native than Array or Object method implementations. Jeez …

It certainly would be nice to have a single source of truth, but there isn’t. Even if you’ve been told otherwise, there is no Vanilla God, my dear. I’m sorry. The only assumption that really holds is that we are all writing Javascript code that aims at performing well in all major browsers, knowing that all of them have different implementations of the same things. It’s a bitch to cope with, to put it mildly. But that’s the premise, whether you like it or not.

Maybe y’all are working on large scale projects that need twitterish performance so that you really see the difference between 850,000 (underscore) vs. 2,500,000 (lodash) iterations over a list per sec right now!

I for one am not. I mean, I worked projects where I had to address performance issues, but they were never solved or caused by neither Underscore nor Lo-Dash. And unless I get hold of the real differences in implementation and performance (we’re talking C++ right now) of lets say a loop over an iterable (object or array, sparse or not!), I rather don’t get bothered with any claims based on the results of a benchmark platform that is already opinionated.

It only needs one single update of lets say Rhino to set its Array method implementations on fire in a fashion that not a single “medieval loop methods perform better and forever and whatnot” priest can argue his/her way around the simple fact that all of a sudden array methods in FF are much faster than his/her opinionated brainfuck. Man, you just can’t cheat your runtime environment by cheating your runtime environment! Think about that when promoting …

your utility belt

… next time.

So to keep it relevant:

  • Use Underscore if you’re into convenience without sacrificing native ish.
  • Use Lo-Dash if you’re into convenience and like its extended feature catalogue (deep copy etc.) and if you’re in desperate need of instant performance and most importantly don’t mind settling for an alternative as soon as native API’s outshine opinionated workaurounds. Which is going to happen soon. Period.
  • There’s even a third solution. DIY! Know your environments. Know about inconsistencies. Read their (John-David‘s and Jeremy‘s) code. Don’t use this or that without being able to explain why a consistency/compatibility layer is really needed and enhances your workflow or improves the performance of your app. It is very likely that your requirements are satisfied with a simple polyfill that you’re perfectly able to write yourself. Both libraries are just plain vanilla with a little bit of sugar. They both just fight over who’s serving the sweetest pie. But believe me, in the end both are only cooking with water. There’s no Vanilla God so there can’t be no Vanilla pope, right?

Choose whatever approach fits your needs the most. As usual. I’d prefer fallbacks on actual implementations over opinionated runtime cheats anytime but even that seems to be a matter of taste nowadays. Stick to quality resources like http://developer.mozilla.com and http://caniuse.com and you’ll be just fine.

Solution 6:

I’m agree with most of things said here but I just want to point out an argument in favor of underscore.js: the size of the library.

Specially in case you are developing an app or website which intend to be use mostly on mobile devices, the size of the resulting bundle and the effect on the boot or download time may have an important role.

For comparison, these sizes are those I noticed with source-map-explorer after running ionic serve:

lodash: 523kB
underscore.js: 51.6kb