May 30, 2013

Haskell Weekly News: Issue 268

Welcome to issue 268 of the HWN, an issue covering crowd-sourced bits of information about Haskell from around the web. This issue covers the week of May 12 to 25, 2013.

Quotes of the Week

  • tikhonjelvis: the lesson is that the fix function exists to "fix" any type problems you may encounter
  • shachaf: The trouble with peano arithmetic is that it stops at 88.
  • Peaker: Python's dynamic nature adds slowness and unsafety, but doesn't actually make things more expressive
  • sj4nz: Programming in weakly-typed languages forever after will feel like working with punch cards. Send in your program to the nodejs interpreter and hope for a result to come back.
  • xplat: if you want to carry your machete all the time and not make people nervous, you need to constantly blaze trails
  • otters: heh, F# is just the unboxed version of F
  • quchen: This was the first time in months that I thought imperatively. Conclusion: 1. it complicated things, 2. it was refreshing
  • cmccann: I still kind of expect that the next standard will be haskell2017 or something, and all it will do is a minor change to lexical syntax of comments that fixes nothing but nevertheless breaks 20% of hackage.
  • cmccann: [on reimplementing cryptography in pure Haskell] writing in Haskell lets you use type safety to ensure that all the security holes you create are subtle instead of obvious.

Top Reddit Stories

Top StackOverflow Questions

Until next time,
+Daniel Santa Cruz

No comments: