|
|
|
|
|
|
by daniel-levin
4137 days ago
|
|
|
I must respectfully disagree that Haskell's memory footprint is simply 'low'. This is because the memory footprint of a given Haskell program is not at all transparent, and Haskell is notorious for leaking memory in a maddeningly opaque fashion [1, 2, 3, 4]. Space leaks might be relatively straightforward to diagnose and fix for a true domain expert, but I would not want to have to rely on someone having such abstruse knowledge in a production application. It goes without saying that a space leak in a production app is a really, really bad thing. Although, I suppose one's choice of Haskell is a function of one's own risk/reward profile. Haskell and its failure modes are hard to understand. That induces extra risk that some people (myself included) might be uncomfortable with. That said, I am now enthusiastically following you guys and hope to see the proverbial averages get sorely beaten. [1] http://neilmitchell.blogspot.com/2013/02/chasing-space-leak-... [2] http://blog.ezyang.com/2011/05/calling-all-space-leaks/ [3] http://blog.ezyang.com/2011/05/space-leak-zoo/ [4] http://blog.ezyang.com/2011/05/anatomy-of-a-thunk-leak/ |
|
|