mostly-adequate-guide VS excoptional

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

> I mean Scala because I guess it actually has it, but worth pointing out it's like 30 LOC to define one for JS, depending on how many convenience methods you want.

Here's one I wrote: https://github.com/sbernheim4/excoptional

I fully believe it to be one of the best Option implementations in JS/TS

https://github.com/sbernheim4/excoptional is an option object for js/ts

One benefit to keeping your value wrapped in a Maybe is that as you transform and manipulate the value and pass it around in your system, you leave it up to the last place in your system that uses the value to define the fallback value in the case of a None rather than defining a fallback value part way through and establish a convention that the fallback value means nothing was found at some other part of your system.

Another benefit to using Maybes is that you avoid the rigamarole of null checks at every call site where you want to use the value. If you have a function that returns null or a value, whenever you call that function you'll always have to add an if guard to validate it's not null. If it is, that function itself may return null, and callers to it will again have to implement the same check.

I wrote a JS implementation of the Option object and the readme has lots of specific examples about these benefits: https://github.com/sbernheim4/excoptional