mostly-adequate-guide VS voila

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

Quick link: https://github.com/voila-dashboards/voila

Humbly recommend when you share a product, you include a link to it ;)

https://voila.readthedocs.io/en/stable/

> Works with CI/CD out of the box. Deploy to vercel, netlify, your own infra.

Jupyter is suited for whatever you want to do with it. Voila exists to enable the use case of re-generating notebooks on a CI/CD system: https://github.com/voila-dashboards/voila

Anyways, seems like the templating is more powerful than the one being offered by Jupyter Notebooks.

Good luck and much success with it :)

i don't understand why everyone isn't just using voila. it's so much better than streamlit or gradio. but that's just my opinion i guess.

Ill have to check it out and see how it compares to voilà and holoviz panel. What I like about Holoviz panel is you can create a data web app from code that resides in a notebook or create a completely standalone app from just plain py scripts, and it supports many different visualization backends. I have found it to be the more flexible and generalizable data web app framework among the others I have come across (like Voilà, Dash, Plotly, and Streamlit).

Any insights what the differences between this and Voila are? https://github.com/voila-dashboards/voila

A nifty little alternative to voila, one might say.

Markdown and/or Voilà https://github.com/voila-dashboards/voila

If you are comfortable working in a Jupyter Notebook you can combine ipywidgets & Voila.