Timeline for Asynchronous Programming in Functional Languages
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Feb 7 at 1:06 | history | suggested | dan | CC BY-SA 4.0 |
fix 404 link
|
| Feb 3 at 11:16 | review | Suggested edits | |||
| S Feb 7 at 1:06 | |||||
| Nov 10, 2013 at 17:05 | comment | added | Gill Bates | Disagree - a fact that program is composed from 'pure' functions doesn't mean that it don't iteract with outside world, it's mean, that every function in a program for one set of arguments will always return same result, and this is (purity) a big deal, because, from practical view - such program will be less buggy, more 'testable', successful execution of functions could be proved mathematically. | |
| Oct 4, 2013 at 12:40 | comment | added | Amogh Talpallikar | Basically after understanding the benefits of functional approach and changing state only when it matters will automatically make sure that even if you work in say something like Java, you know when to modify state and how to keep such things in control. | |
| Jan 22, 2011 at 2:34 | comment | added | 9000 | Also: looking at Erlang helps. The language is very simple, pure (all data is immutable) , and is all about asynchronous processing. | |
| Jan 22, 2011 at 1:54 | history | answered | Chris Smith | CC BY-SA 2.5 |