funflow VS rio-orphans

funflow is a cool library for writing "workflows", but basically it's a library that implements caching. So if you have a process that reads a file A, does transformation A → B, then does B → C, then C → D, then writes D to disk, each step of that will be cached to disk and you won't need to redo the A → B step if your program crashes during the B → C step.

You might wanna check out funflow

Funflow: https://github.com/tweag/funflow

https://github.com/commercialhaskell/rio#language-extensions which is cited as an example in simplehaskell's page on recommendations.

> Can we move to a better standard lib? Here Snoyman has put forward a great effort by releasing his classy-prelude, but iirc he also stopped using it.

He mentioned https://github.com/commercialhaskell/rio in the 1st article, it's interesting, I wasn't aware of it. (I am using classy-prelude but I might try it out.)

rio

It's worth mentioning that Snoyman's "Boring Haskell" is actually a fairly moderate position: if you look at his suggested list of language extensions, it's pretty broad (and fairly reasonable in my view).

via ByteString was recommended by Snoyman in the post Beware of readFile (referenced in the Haskell: The Bad Parts, part 1 too). But this has got a disadvantage compared to Data.Text.IO combined with hSetEncoding. This might be a good time to update Beware of readFile, u/snoyberg.