3 ms·
The correctness argument is interesting, but certainly plenty of critical-to-be-correct software has been written in imperative languages too. I'd like to see s
by cageface 17y ago
The correctness argument is interesting, but certainly plenty of critical-to-be-correct software has been written in imperative languages too. I'd like to see something closer to hard numbers on bug counts, man hours etc on similar projects in Haskell or ML vs C++ or Java, for instance. I realize it's hard to find a truly apples to apples comparison here.
The uptake of FP in finance is interesting. I'd like to hear more about exactly how FP is being used in these contexts. Is it used in a narrow, specialized domain or broadly? To what extent are the advantages of FP in this domain realizable in others? Is FP only suitable for small, elite teams or can mainstream programmers pick it up with the right training? To what extent does the less mature or less conventional toolchain offset the advantages of the language itself?
- dons 17y agoCheck the experience reports from CUFP for such examples: * http://haskell.org/haskellwiki/Haskell_in_industry#Haskell_in_Industry http://haskell.org/haskellwiki/Haskell_in_industry#Haskell_i... Barclay's Capital has written a journal article on why they use FP (Haskell in this case): http://lambda-the-ultimate.org/node/3331 http://lambda-the-ultimate.org/node/3331
- cageface 17y agoThanks for the links. Looks like some good afternoon reading. It's interesting that the Barclay's article discourages overuse of the point-free style. In my attempts at learning Haskell I've also found heavy use of this style can make Haskell code hard to understand.