"Because community. I really want Business4s to be welcoming to all parties without picking favorites, even if I have mine. But convergence if effect systems isn't happening on its own, and in the meantime, hardcoding IO puts up a wall between Workflows4s and people who'd otherwise use it."
"Ox / direct-style friction - bridging Loom-based effects through IO.blocking / unsafeRunSync fights the underlying model and adds context-switching overhead just to satisfy the IO signature."
"There were specific use cases too: Marcin told me he intends to run Workflows4s on AWS Lambda in as lightweight way as possible - IO plus its runtime was a hefty tax there."
"The technical arguments alone wouldn't have been enough - they're real but mostly manageable through cats-effect interops, with acceptable tradeoffs. Combined with the community motivation though, this had to be solved."
The resolution of effect types issue #59 was crucial for the Business4s project, aiming to create a welcoming environment for all users. Hardcoding IO created barriers, and addressing this issue was essential for broader adoption. Technical motivations included reducing overhead from Loom-based effects and avoiding dependency issues with ZIO. The timeline of the resolution spanned from April 2025 to April 2026, involving community discussions and collaborative efforts to implement a solution that balanced technical needs with community goals.
Read at Medium
Unable to calculate read time
Collection
[
|
...
]