aboutsummaryrefslogtreecommitdiff
path: root/chapter
diff options
context:
space:
mode:
authorNat Dempkowski <natdempk@gmail.com>2016-12-03 21:12:51 -0500
committerNat Dempkowski <natdempk@gmail.com>2016-12-03 21:12:51 -0500
commitb0882145fc373e1d85049be00bdddedd24ed78bd (patch)
tree50a737a61d33727bfc9e7db6d3c39e24e6060747 /chapter
parent4d373306b89abca4d7eb2204bcd397b364b167f5 (diff)
Add Cloud Haskell section heading
Diffstat (limited to 'chapter')
-rw-r--r--chapter/3/message-passing.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/chapter/3/message-passing.md b/chapter/3/message-passing.md
index 2b56024..bb903b9 100644
--- a/chapter/3/message-passing.md
+++ b/chapter/3/message-passing.md
@@ -57,6 +57,8 @@ Erlang also seeks to build failure into the programming model, as one of the cor
These primitives can be used to construct complex hierarchies of supervision that can be used to handle failure in isolation, rather than failures impacting your entire system. Supervision hierarchies are notably almost the only scheme for fault-tolerance that exists in the world of actors. Almost every actor system that is used to build distributed systems takes a similar approach, and it seems to work. (Example of Erlang reliability or something would be good here)
+## Cloud Haskell
+
## Scala Actors
Scala Actors brings lightweight Erlang-style message-passing concurrency to the JVM and integrates it with the heavyweight thread/process concurrency models. This is stated well in the original paper about Scala Actors as "an impedance mismatch between message-passing concurrency and virtual machines such as the JVM." The authors say that VMs usually map threads to heavyweight processes, but that a lightweight process abstraction reduces programmer burden and leads to more natural abstractions. The authors say that “The user experience gained so far indicates that the library makes concurrent programming in a JVM-based system much more accessible than previous techniques.”