Selecting Features from the Effect Ecosystem: Balancing FP and Non-FP Approaches
Is it possible to pick and choose features of the effect ecosystem to use without buying into all of it?
Eg: I like how DI is done, Maybe/Option monads, but I'm still nervous about going "all in" so to speak. I would prefer to continue using promises in some of my interfaces, in combination with a library like rxjs/wonka.
For a couple of reasons:
- too much FP will make the code difficult to decipher for non-fp programmers
- there's added risk in placing all my bets in one basket so to speak. I prefer to use a mix of libraries rather than a single "framework".
Is this realistic? Or will there be too much friction if I'm cherry picking features?
Eg: I like how DI is done, Maybe/Option monads, but I'm still nervous about going "all in" so to speak. I would prefer to continue using promises in some of my interfaces, in combination with a library like rxjs/wonka.
For a couple of reasons:
- too much FP will make the code difficult to decipher for non-fp programmers
- there's added risk in placing all my bets in one basket so to speak. I prefer to use a mix of libraries rather than a single "framework".
Is this realistic? Or will there be too much friction if I'm cherry picking features?
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
