Loading user information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading user information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

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

42 minutes, 51 seconds


Right click “Save as…”

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.

Follow the discussion

  • Oops, something didn't work.

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

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

  • ZuraZura

    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.

  • @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!

  • BenBen

    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).

  • ZuraZura

    @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.

  • Marek SieradzkiMarek Sieradzki

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

Remove this comment

Remove this thread


Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.