rio-orphans
haskelldb
| rio-orphans | haskelldb | |
|---|---|---|
| 6 | 1 | |
| 836 | 99 | |
| 1.0% | - | |
| 0.0 | 0.0 | |
| over 1 year ago | almost 5 years ago | |
| Haskell | Haskell | |
| MIT License | BSD 3-clause "New" or "Revised" 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.
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.
haskelldb
-
Why exactly I want Boring Haskell to happen
HaskellDB was principled but the codebase was somewhat bitrotted, it had dubious denotational semantics, it was possible to write crashing queries. and only worked with a special "record" form data types that it had cooked up. On the other hand once one accepted the special "records" everything else looked like familiar Haskell. Queries were written in do-notation.
What are some alternatives?
basic-prelude - An enhanced core prelude, meant for building up more complete preludes on top of.
HongoDB - A Simple Key Value Store
time-warp
database-migrate - database-migrate haskell library to assist with migration for *-simple sql backends.
ghc-proposals - Proposed compiler and language changes for GHC and GHC/Haskell
haskelldb-connect-hdbc-catchio-mtl - Bracketed HDBC session for HaskellDB
bytestring-progress - A Haskell library for tracking the consumption of lazy ByteStrings
mywatch
cond - Basic conditional operators with monadic variants.
perdure - Robust persistence for typed immutable data
ifcxt - constraint level if statements
classy-influxdb-simple