1. 17
  1.  

  2. 7

    TL;DR:

    1. 5

      It’s postgresql-simple. That’s why you couldn’t find it.

      I haven’t looked at Opaleye. Thanks for the recommendation!

      1. 2

        Thanks! Here’s a link: postgresql-simple. I couldn’t find it because a Hackage search for “postgres” didn’t return it.

      2. 4

        postgresql-simple is pretty much just basic bindings to libpq while opaleye is a larger library for building up SQL queries programmatically.

        1. 3

          Acid State is so damn cool. I really think the world needs more libraries that enable fault-tolerant computation like that for other languages. Engineers often have such an irrational fear of the disk, and the things they build just fall over in downstream failure/backpressure situations or traffic spikes when they accumulate too much memory. A transactional persistent log can work so well and when you’re writing and consuming sequentially it’s extremely efficient.

        2. 4

          I’ve started porting Clay to PureScript: purescript-css

          1. 1

            Hell yes! Thank you.

          2. 2

            Gotta say, I don’t really see the benefit of Clay over Sass or Less…

            1. 4

              The benefit of Clay over other CSS pre-processors (like Sass or Less or purescript-css that @puffnfresh mentions) is that it’s just Haskell. You don’t have to get another language (usually JavaScript) involved in your build process.

              1. 1

                But sass compiles before it even hits the server, Javascript is almost never involved. Why not use tools built for the purpose?

                1. 4

                  Clay is built for the purpose. A benefit is that you have a full programming language and composable operators to create CSS. It’s much more powerful than LESS, which is a benefit and a drawback.