Workflow
rio-orphans
Our great sponsors
Workflow | rio-orphans | |
---|---|---|
1 | 6 | |
42 | 836 | |
- | 1.0% | |
0.0 | 0.0 | |
almost 8 years ago | about 1 year ago | |
Haskell | Haskell | |
BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Workflow
-
Event Sourcing
I was part of that debate, I remember a rather interesting point of discussion: Is the main operation "apply" or "dedup"
Apply seems to be the common notion of event sourcing: There is a function apply that takes a state an event and yields a new state. Then, starting in an init state and iteratively applying the entire event history, boom, latest state restored.
Dedup has a lot of charm though: Run and rerun your code, if that step of your code is executed for the first time (no corresponding event in the event history) execute the step and store its result as an event in the history, however, if that step of your code is executed for the second, third time (there is a corresponding event in the event history) do not execute the step and return its result from the event in the history. The Haskell Workflow Package (https://hackage.haskell.org/package/Workflow) is a good example
Temporal follows the second approach, so "proper" Event Sourcing? You be the judge :)
rio-orphans
-
Haskell IHP Framework, from a Technical and Business Perspective
https://github.com/commercialhaskell/rio#language-extensions which is cited as an example in simplehaskell's page on recommendations.
- [ANN] text-display 0.0.1.0: A typeclass for user-facing output
-
Haskell: The Bad Parts, part 2 (2020)
> 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.)
-
Are similar effects system like in Scalas ex: Cats Effects, ZIO etc also available in Haskell?
rio
-
Why exactly I want Boring Haskell to happen
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).
-
Haskell The Bad Parts Part 1
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.
What are some alternatives?
cloud-haskell - This is an umbrella development repository for Cloud Haskell
basic-prelude - An enhanced core prelude, meant for building up more complete preludes on top of.
unliftio - The MonadUnliftIO typeclass for unlifting monads to IO
time-warp
effect-monad - Provides 'graded monads' and 'parameterised monads' to Haskell, enabling fine-grained reasoning about effects.
ghc-proposals - Proposed compiler and language changes for GHC and GHC/Haskell
record - Anonymous records
bytestring-progress - A Haskell library for tracking the consumption of lazy ByteStrings
lens-tutorial - The missing tutorial module for the lens library
cond - Basic conditional operators with monadic variants.
monad-time
ifcxt - constraint level if statements