2 ms·
Without getting into a hugely semantic debate, I was using side effect imprecisely to mean the opposite of a pure function. Many FP paradigms (including Haskel
by kasey_junk 12y ago
Without getting into a hugely semantic debate, I was using side effect imprecisely to mean the opposite of a pure function.
Many FP paradigms (including Haskell's) impose an overhead when doing operations that are not pure. In the case of a SMB clone a huge percentage of the work of the program may end up not being pure, therefore a large overhead may be imposed. Further, many of the advantages of FP paradigms (including Haskell's) are dependent on pure functions.
In the case of a SMB clone, a large percentage of the application may be intended to be impure, therefore the "worst case scenario" comment.
- deleted 12y ago[deleted]
- dllthomas 12y ago"Without getting into a hugely semantic debate, I was using side effect imprecisely to mean the opposite of a pure function." That's the second sense I described. It's only meaningful if you're actually talking about a particular function. And you're still left with the question of the actual domain of the function. Semantics, but relevant semantics. "Many FP paradigms (including Haskell's) impose an overhead when doing operations that are not pure. In the case of a SMB clone a huge percentage of the work of the program may end up not being pure, therefore a large overhead may be imposed. Further, many of the advantages of FP paradigms (including Haskell's) are dependent on pure functions." That's somewhat true of FRP, basically false about Haskell IO generally, but either way if you can do it in PyGame someone can do it in Haskell - it's mostly a matter of working in a high level language, not a matter of functional-programming-imposed overhead. I would recommend listening to what John Carmack had to say about implementing games in Haskell (and also Lisp, IIRC).