iter-ops VS ramda

I think I'm gonna stick with iter-ops, where I can use map without Promise resolution, so I can execute any resolution strategy described there.

So I’ve branched away from iter-ops, and into iter-ops-extras, coding away with no strings attached.

Is there a good reason to choose this solution over rxjs or iter-ops?

That's why I went an extra mile within iter-ops to provide such performance monitoring tools as pre-defined operators:

Someone posted this recently. Maybe it'll help?

P.S. I started within the esm branch there, but didn't make much progress. In case you want to re-use that branch ;)

Check out Aggregates, it explains why things like groupBy or sort aren't there.

JS supports functional programming very well, but I do miss a more native way of processing Iterators without adding a lib like iter-ops, since it is clunky (and a most likely a performance killer) converting Sets and Maps into Arrays back and forth.

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!)