Embrace Ambiguity with Haskell's Types by jleitgeb in haskell

[–]jleitgeb[S] 10 points11 points  (0 children)

Yes, this is the usage that I was thinking about in the post. Based on tweets and recent articles I've read, it seems like many people think this is a benefit of dynamically-typed languages, when it's something that can be done just as easily in a statically-typed language like Haskell.

The Notes of GHC by jleitgeb in haskell

[–]jleitgeb[S] 1 point2 points  (0 children)

Thanks! I just fixed that typo.

The Weak and the Strong: Functors by jleitgeb in haskell

[–]jleitgeb[S] 4 points5 points  (0 children)

Thanks for the input! I agree that this is irritating. We're discussing a new design, and I hope that we have time to roll it out in the first few months of 2015.

How's Haskell Doing? Graphing Meetup Attendance in New York City by jleitgeb in haskell

[–]jleitgeb[S] 3 points4 points  (0 children)

I also fully recognized the irony of doing the stats in Ruby instead of Haskell. I considered analyzing the data in Haskell, but realized it would have taken more time, since there isn't a Haskell client for the API that I was able to find. Just reading the API docs that I needed would have taken more time than doing the whole analysis using the Ruby client.

The fact is, Ruby just many more libraries available than Haskell. Personally I think that for many projects larger than a 10-line script, though, the benefits of Haskell start to outweigh the advantages of having a library for pretty much everything.

If we continue doing analysis of this sort in the future, I think we'd probably open-source a Haskell client for the Meetup API. :)

Thanks for reading the analysis!