Hi @tim-smart

Sandro here (fpdart's author) 👋

I took a look at you ZIO implementation and it looks really promising. I think there is some overlap with fpdart's API (on effects, IO, Task, TaskEither, etc.).

This situation looks similar to fp-ts + effect-ts: fp-ts originally providing IO, Task, TaskEither (just like fpdart), while effect-ts with Effect (ZIO).

I think it could be interesting considering a consolidation of both our implementations (fpdart + ZIO). I really like the ZIO approach:

• One class for all effects (ZIO instead of IO, Task, etc.). This makes easier (possibly) to explain one concept ZIO instead of many different classes
• Easier to maintain (one implementation instead of many similar method in different effects)
• Aligned with effect-ts and ZIO (Scala), possibly sharing some documentation and resources

What I would suggest is a possible integration of ZIO inside fpdart (for a possible v1.0 release?).

@tim-smart what do you think about this? Am I correct about the similarities between ZIO and fpdart's effects? Is there something that the ZIO implementation is missing compared to fpdart's effects?