Hi, I am building a framework for interactive notebooks (like Jupyter Notebooks, but focused on modern web development tooling and Org mode - orgp.dev).
This enables me to share my creative thinking.
In this series of articles, I am migrating Starplot (a Python library for creating star maps) to JavaScript while exploring all the related concepts and knowledge around history, math, and astronomy.
I’ve added a bit of narrative-imagine a Tuareg sitting beneath a crystal-clear sky in the desert at night.
Let me know what you think and if you have any questions.
I’m not claiming any right in naming after Ancient Greek gods.
But wanna say that I choose the “same” name for a related goal project https://github.com/Ideabile/ermes
I still need to wrap my head on your use of generics, but yours looks more flexible than the static type approach that other libraries (include RxJS) implements, does your pipe support types for any length of arguments? Does require a specific version of TypeScript?
Thanks for this article, I was just talking with my colleagues about it. And didn't find something simple to share with them, so this was just what I needed.
I think DRY is a good thing in some cases, but you should careful consider when something is worth to DRY and when rather WET gives you the best tradeoff for isolation.
My metrics to decide is to stick in favour of the Single Responsibility Principle.
If DRY means compromising it, most likely is not worth it.
This article just make me feel stupid, which probably I am.
The only pragmatic argument that I could understand is the hard-wiring “issue”; which IMO is not part of FP and neither OOP but just a consequence that explicit intents are simpler than implicit intents.
I understand that this is to introduce to a novelty approach that Multix offers with cats.
But to be fair, not as sofisticate as Multix, Dependency Injection tries to tackle the hard-wiring constraints of imperative.
What I take from FP is Composition rather than Chaining, which much more flexible than the OOP counterpart, inheritance.
I was expecting to learn something new but I just jump in a spooky vocabulary that rather teach me something just waste my time.
The point stand, Multix might be a fabulous approach in coding, but this article failed to give any practical introduction to it, while claiming his superiority in something that totally didn’t resonate with me.
If your mission is getting Multix adopters I will invite you to shift your focus from language/tone/academical complexity; to something more simple, what does it solve?
So I built Gigi, a control plane for autonomous AI development.