Rationale for Extending Effect Program Boundaries
Biggest question I have is what is the rationale for extending the boundary of Effect programs. For example, I understand Effect can basically run a program, but why do some Remix examples wrap the action and loader with Effect? Why not just run the program within the request handler and keep the Effect boundary limited to that. In other words, what benefits are there to extending the boundary of the Effect program further?
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
