just VS ramda

just-diff

You can roll your own or use a utility library. A simple zero-dependency library would be something like just-group-by [1]. Although I now prefer remeda [2] as it seems to have the best typescript support, especially the strict variants such as `grouBy.strict`.

[1] https://github.com/angus-c/just#just-group-by

Tree-shaking doesn't help much when the tree-shaken implementation is so bloated.

Here's the one you referenced, lodash.chunk: https://unpkg.com/lodash.chunk – 140 lines after removing comments and whitespace.

That's pretty small compared to a lot of the lodash utilities. Try spot-checking a few on unpkg.

I prefer angus's `just` utilities: https://github.com/angus-c/just

I absolutely love this. When I need some Lodash alternative I'll usually reference angus-c/just but I am definitely bookmarking this for next time.

The just set of utility functions are really nice to use. https://github.com/angus-c/just

Just doesn't have everything but it's pretty good

One of my favourite "libraries" are the "just" packages, where each part of the library is it's own simple package with zero dependencies (https://github.com/angus-c/just) so you essentially just npm install the specific thing you want - which is generally a single function.

If the code should, as you say, be 5 lines, why take on a dependency at all? By doing so, you end up with a catch-all solution that does almost nothing other than JSON.stringify your args, which is extremely poorly optimized to handle many situations, e.g. one of your args is a primitive and the other is a large config object.

JavaScript is great for point-free programming! Make sure you check out Ramda.js https://ramdajs.com/

It’s fun in the sense that solving a puzzle is fun, but I avoid it for anything I need to maintain long-term.

But it’s good practice for understanding combinators which is useful for some kinds of problems.

This is very cool. I remember I got sucked into things like Ramda going down this functional programming rabbit hole :-)

https://ramdajs.com/

To create our pipeline, I'm going to use the pipe function from the NodeJS ramda library instead of building my own.

Other libraries to check out are pratica and ramda

I recently took ownership of the new types/ramda repo. This repo is re-exported by @types/ramda and is the first step to bringing type definitions for ramda in-house. We're already hard at work correcting major issues, adding full currying support, and general bug fixes

I'm going to be honest. You probably don't need to use currying in JavaScript. In fact, trying to fit it in your code is going to do more harm than good, unless it's just for fun. Currying only becomes useful when you fully embrace functional programming, which, in JavaScript, means using a library like Ramda instead of the standard built-in functions.

Lodash gets so many things wrong I’d rather not see it in most projects. I appreciate a good utility library for JS projects but my go-to choice has to be Ramda[1]. Every function it exports is curried and works great with pipe which enables me to write highly reusable and composable functions in pointfree notation. I have never been as productive with lodash, and I find the functional style easier to read

[1] https://ramdajs.com/

Do note though that ramda is different from rambda. 👍 (Granted they are very similar!)