1. 10
  1.  

  2. 6
    1. 3

      Looks very nice, but how do I type the Unicode? Would this just be for display?

      It seems to me that once you start getting fancy with the inputs, you may as well need an IDE to make those Unicode characters easily accessible, and then we’re just a hop, skip, and a jump away from visual programming languages.

      1. 4

        This isn’t an entirely serious project to begin with and the unicode-ification would probably be generated from the types if it were a serious thing.

        Just a (working) experiment in visualization of arrows in Haskell.

        We don’t even really use arrows that much, other things proved to be nicer abstractions most of the time.

        1. 2

          Fair! I actually end up drawing diagrams that look fairly similar to the ones you’ve generated when I need to reason about data streams. Maybe this could find more traction as a general data transformation visualization tool?

          1. 2

            Oh I didn’t write down the unicode version, kamatsu from the Reddit thread did. Sorry, should’ve said so.

            It could be useful I guess, but only if you’re using Haskell?

            1. 2

              True, I haven’t taken a very deep look at it. I’m working with Django right now and a tool like this could de-mystify some of the QuerySet API.

              1. 3

                You need types mate.

                I used to be primarily a Python and Clojure user. I’ve been teaching Haskell for a year now. This is how I teach Haskell: https://github.com/bitemyapp/learnhaskell

                1. 2

                  I’ve always been a bit leery of trying to do webapps in FP. It seems to me like webapps are designed around mutable state, and Haskell needs a lot of workarounds to make it work.

                  That being said, bookmarked. I need to bite the bullet and do more than Hello World in Haskell

                  1. 3

                    It seems to me like webapps are designed around mutable state,

                    No computable problem is necessarily about mutable state.

                    Haskell needs a lot of workarounds to make it work.

                    Nope.

                    Some cheap-n-cheerful examples:

                    http://hackage.haskell.org/package/scotty

                    http://bitemyapp.com/posts/2014-08-22-url-shortener-in-haskell.html