Functional-Light-JS VS ramda

Repository: getify/Functional-Light-JS

Functional-Light JS

And if you want to get to the "advanced" level of Javascript => https://github.com/getify/functional-light-js

I didn't really understand FP until I read Functional Light JavaScript by getify/Kyle Simpson. It is so well written and approachable by mere mortal coders. I'm not an FP wizard, but it is the coding paradigm I mostly use now. I've even adapted some aspects (e.g. composability) to the CSS I write using `var()`.

You can buy the book or read it on GitHub:

http://fljsbook.com/

https://github.com/getify/functional-light-js

Now he taught himself functional programming and GAVE ME HOMEWORK. I'm supposed to read this https://github.com/getify/Functional-Light-JS

Whenever I come across a cool concept in Computer Science, I try to think how to use it in real life scenarios. I've recently read Kyle Simpson's highly recommended book "Functional-Light JavaScript" that manages somehow to be thorough, innovative and fun to read at the same time. Near the end of the book Simpson discusses Monads, and demonstrates the concept with a cute example that is also a parable about the importance of humility and knowledge sharing. While I found this lesson valuable, I tried to come up with an example that could be useful in a real project.

They can, and they do quite nicely. A common approach is to be functional until it is no longer practical or efficient or fun, then wrap it in an imperative style. This is what Kyle Simpson imparts in Functional Light JS.

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