3 ms·
"Avoid side-effects" is #1 IMO. Everything else stems from it.
by akkartik 17y ago
"Avoid side-effects" is #1 IMO. Everything else stems from it.
- jacquesm 17y agoThe funny thing is after playing around with functional programming for a bit simply out of interest I've found that I've definitely changed to 'avoid side-effects' in my 'regular' programming as well, and it really helps to do that.
- loup-vaillant 17y agoAssignment is evil (most of the time): http://news.ycombinator.com/item?id=1117217 http://news.ycombinator.com/item?id=1117217 That's because it's relatively rarely needed: http://www.info.ucl.ac.be/~pvr/paradigms.html http://www.info.ucl.ac.be/~pvr/paradigms.html (I don't recall the HN submission.) The paper says that any feature in a programming language makes it more difficult to analyse it. First class functions are one of them. Named state (with assignment) is another. So, when such a feature isn't needed (for, say, modularity), the complexities it introduces are unnecessary.