I like Ramda[1] better than both underscore or lodash because of it's argument ordering (function first) and auto-currying[2]. It's 7kb minified and gzipped. [1] http://ramdajs.com/ [2] https://buzzdecafe.github.io/code/2014/05/16/introducing-ram...
I don't follow Underscore but whoever wrote this title (currently "Underscore 1.8 makes last minute breaking changes to master without discussion") must really have an axe to grind, and it seems inappropriate for HN. Doesn't really set the tone for any constructive discussion.
Yeah, and linking to a PR risks a bunch of parties w/o a real stake in the project piling on and shitting up the PR. Really poor form, OP.
I like Ramda[1] better than both underscore or lodash because of it's argument ordering (function first) and auto-currying[2]. It's 7kb minified and gzipped. [1] http://ramdajs.com/ [2] https://buzzdecafe.github.io/code/2014/05/16/introducing-ram...
I like Ramda as well, currying was a feature I didn't expect to use as often as I did.
I don't follow Underscore but whoever wrote this title (currently "Underscore 1.8 makes last minute breaking changes to master without discussion") must really have an axe to grind, and it seems inappropriate for HN. Doesn't really set the tone for any constructive discussion.
Yeah, and linking to a PR risks a bunch of parties w/o a real stake in the project piling on and shitting up the PR. Really poor form, OP.
shitting up the PR
Good people of HN, this phrase deserves your upvotes.
A couple things: - The actual difference (minified and gzipped) is 17.6 KB vs. 5.7KB. - Lodash is written modularly so you can import only the methods you actually need. - In order to "lose some weight" (as Jeremy Ashkenas called it), underscore dropped several methods that people really wanted (including other contributors). - Also to cut down the size, several major pieces of functionality is not broken in older ve…
With regard to size, the gzipped size isn't the whole story - more code results in more processing time and memory usage.
True, but probably not the magnitude of difference you should be worried about.
I don't follow Underscore but whoever wrote this title (currently "Underscore 1.8 makes last minute breaking changes to master without discussion") must really have an axe to grind, and it seems inappropriate for HN. Doesn't really set the tone for any constructive discussion.
The submitted title ("Underscore 1.8 makes last minute breaking changes to master without discussion") broke the HN guidelines by editorializing the title. We changed it to the article title, such as it is. If any of you wants to suggest an accurate and neutral title that is better, we can change it again.
If you care about filesize, you'll probably optimize as much as possible. You can do this with Lodash using modular imports. There's little upside in hosting a light version, and fragmenting the docs. Min/max'ing on filesize lets you save 15 kB, or 0 kB. Creating a light build that saves 5 kB is a maintenance cost with a poor ratio relative to reward.
> If you care about filesize I don't care about filesize. I care about code complexity. The more crap you add to a page, the slower it will run. You also get a higher probability of conflicts and problems in the long run. If you need something, you need something. But if you don't and you just throw it in there, you're asking for problems down the road.
For an example of cherry-picking lodash modules see
I like Ramda[1] better than both underscore or lodash because of it's argument ordering (function first) and auto-currying[2]. It's 7kb minified and gzipped. [1] http://ramdajs.com/ [2] https://buzzdecafe.github.io/code/2014/05/16/introducing-ram...
https://www.npmjs.com/package/lodash-fp Don't know how they compare though.
To be fair: Underscore doesn't follow semver, so breaking changes between versions should be expected. This thread just seems like an excuse to pile on jashkenas and promote lodash.
It is released and consumed via 2 package managers that mandate the use of semver.