A Means to Many Ends: 10+ Years of Haskell at Galois

Download this episode

Download Video


Galois started out using Haskell because it was our first love. This talk will be about why we *still* use it. Yes, we still love Haskell, but as the Beatles said, love don't pay the bills. I'll present some recent projects that show different aspects of our use of Haskell, giving a sense of what Haskell brings to the table, closing with a more nuanced answer to the question of why we still use -- and love -- Haskell.







Available formats for this video:

Actual format may change based on video formats available and browser capability.

    The Discussion

    • User profile image

      I'm very fond on Haskell, and I'm looking forward to seeing this talk. When the video will be available? Smiley

    • User profile image

      Oh, Is finally online! Fantastic talk, really enjoyed it!

    • User profile image

      While I agree that Haskell is really nice in small book examples, I have to admit, now as an insider, that "in large"/real world, especially when you have to use multiple monads - i.e. monad transformers, it tends to very unreadable and clumsy code.

    • User profile image

      @Zura: Hi, are you from a company that uses Haskell? It would be interesting to share your outlook and opinion about the language, maybe in a blog post. It's always nice to have feedback from who uses Haskell in the "Real World". Bye and Good Easter day!

    • User profile image

      I guess by that definition I'd also qualify as an "insider", and I have to say that my experience has been very different from yours. Monad transformers certainly don't solve all the world's problems, but I've not found that they lead to unreadable or clumsy code. (And it's worth pointing out that Monad transformers are just one of a whole suite of approaches to handling effects - different approaches being suitable in different situations).

    • User profile image

      @CharlesStain: Hi. Thanks, I hope you had a good Easter day as well!
      I'm not from the company that uses Haskell and I'm not a blogger/writer :)
      I acquired this impression after fairly long time playing with Haskell. As I already expressed, it is really nice in "academic" use cases.

      @Ben: Besides my personal experience, I feel the same regarding many non-trivial "real world" Haskell projects you can find on the net.

    • User profile image
      Marek Sieradzki

      If monad stack you chose leads to unreadable/clumsy code you probably chose wrong stack in the first place.

    Comments closed

    Comments have been closed since this content was published more than 30 days ago, but if you'd like to send us feedback you canĀ Contact Us.