static-land VS mostly-adequate-guide

There are respective fantasy land and static land specs, with the law conformance checks.

A big poster child of functional style in JS-land is actually implemented on top of textbook OOP (Array.prototype.map/filter). For anyone interested in the gore details of functional polymorphism, look no further than the comparison between fantasy land and static land. Basically, it boils down to a simple fact: functional algebra constructs can be implemented in terms of other functional algebra constructs, but when push comes to shove, the most efficient Array map implementation is not going to be the same thing as a map implementation for any other data structure (Stream, Optional, whatever) and you can't have a magical compiler optimize under the hood for you in Javascript, because well, Javascript. So functional polymorphism has to be shoved somewhere, and as it turns out OOP happens to be a good complement for that conundrum.

My goal with hkts is two-fold. First, to learn more about functional programming by implementing some common type classes (specifically, the ones defined in the static-land spec). Second, to put together a pragmatic, easy to read/understand library of tools based on fp-ts, io-ts, and monocle-ts that are deno native.

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...