Considering Effect's Impact on Application Architecture and Dependency Management
Would you say that it is the case that once you start using effect throughout your application, you are tied to it? I'm used to abstracting such dependencies to protect my core application logic in a clean architecture style.
I may be missing something, like wrapping pure non-effect domain logic in effect adapters in my infra layer?
I may be missing something, like wrapping pure non-effect domain logic in effect adapters in my infra layer?
