Since the infrastructure is going through major ch...

# arrow

[CLOVIS]

Since the infrastructure is going through major changes at the moment, do you think it's the correct time to try to introduce Arrow to a project, or should i wait a few months until it calms down? (Taking into account that this project doesn't have any time limitation so there's no issue with waiting)

[CLOVIS]

Basically I have a codebase that massively uses coroutines and exceptions, and sometimes in the future I'd like to replace every exception by Either and similar concepts, but right now looking at the channel it seems like if I try to use anything advanced it might break soon, so it might be better to wait until Arrow Meta and comes along to streamline everything

[raulraja]

Try to keep everything suspend and introduce IO only for concurrency

[raulraja]

in the future the concurrent api may also be projected directly over suspend in which case all you had to do is eliminate wrapping since its simpler

[raulraja]

IO will still be supported so you could migrate to a full suspend based API once available any time.