attoparsec-conduit VS FS2

> makes me think that there aren't any conduits that have more data than can fit in memory on a single machine

Just because you can dedup a conduit doesn't mean you have to. We use conduits for streaming gigabytes-large files while staying within megabytes of memory use – ensuring that is one of the main selling points of libraries like conduit: https://github.com/snoyberg/conduit#readme

Recently, CE3 has had similar issues reported across multiple repositories, almost an epidemic of reports!

Thanks for the explanation!

So it's pull based and not push based like most other streams lib.

Does maybe someone know how this compares to FS2 or Iteratees than? (Both are also pull based streaming solutions).

https://fs2.io/#/

https://en.wikipedia.org/wiki/Iteratee

Looks quite similar to me. Is the Scala FS2 lib maybe even a clones of the Haskell solution? Or are they different in important aspects?

Most important/known: * https://http4s.org/ - an HTTP client/server * https://github.com/typelevel/fs2 - streaming * https://github.com/tpolecat/doobie - JDBC

On the contrary, switching to the functional mindset, with something like Typelevel Scala3 and respective cats and cats-effect fs2 frameworks, helps to rethink a lot of designs and development approaches.

fs2 for streaming.

Finally, the last chapter has been rewritten to be based on some of the main design ideas from FS2 (https://fs2.io), which I hope will be more approachable than the 1st edition.

Just to clarify, is your doubt about the meaning of the api, or do you think you have found a bug? In either case, you can also open a Github discussion https://github.com/typelevel/fs2/discussions.

Another more reactive solution would to use signals, as in FPR sinal network. fs2 implements this very nicely here https://github.com/typelevel/fs2/blob/8b285a6b54c63d43ed6aa3bb91365652035c90e5/core/shared/src/main/scala/fs2/concurrent/Signal.scala

Assuming the bug mentioned here is https://github.com/typelevel/fs2/issues/2568, we came up with a partial fix in a day (https://github.com/typelevel/fs2/pull/2569) and a complete fix in 2 days: https://github.com/typelevel/fs2/pull/2572. Note the original bug was opened on a Saturday. :)