Functional-Light-JS VS mostly-adequate-guide

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.

This project might serve as inspiration: https://github.com/MostlyAdequate/mostly-adequate-guide

i like reading this book directly from github with dark mode, also the subheading don't work in the gitbook website and gitbook is abandoned, here's the github link: https://github.com/MostlyAdequate/mostly-adequate-guide/blob/master/SUMMARY.md

It’s been a while since I focused on FP, but I recall finding this useful quite often and gleaning the concepts from it relatively easily.

https://github.com/MostlyAdequate/mostly-adequate-guide

I found a lot of articles like the OP, and ultimately they left me confused about the benefits in the beginning. I found it more useful to avoid one off articles and dig into larger pieces of work where the author put in much more care.

On the book front, there are two that I am fond of which have a focus on JavaScript and FP, Professor Frisby’s Mostly Adaquate Guide, and Functional Light JavaScript. They are nice practical books that help you lean into JS’s strength as an FP language while writing real code.

So, this is going to be an uphill battle for you. I suggest you actually learn Haskell first, and then you'll be able to apply its lessons to TypeScript.

Its tricky because these are patterns that are familiar in Haskell but are not really taught in other settings.

Additionally, to really learn these, you need to experiment with them. Use them. etc. That's pretty hard to do if the learning resources are mostly in haskell and you don't really understand it.

Alternatively, this might help: https://github.com/MostlyAdequate/mostly-adequate-guide

Also alternatively, what I would do is just go slowly through the fp-ts code. Look at it a piece at a time and slowly grow your understanding.

This may also help https://www.amazon.com/Domain-Modeling-Made-Functional-Domai...