aboutsummaryrefslogtreecommitdiff
path: root/chapter/4
diff options
context:
space:
mode:
authormsabhi <abhi.is2006@gmail.com>2016-11-28 17:12:45 -0500
committerGitHub <noreply@github.com>2016-11-28 17:12:45 -0500
commit75eafaea4784dd5a1c883720929ef35e465b5a4d (patch)
tree25bf0c81e7d3b2b9e0d05c0d22a50c2d9a47315e /chapter/4
parente2e0995491d8f3588d6214a2b21351063f17e9e3 (diff)
Update dist-langs.md
Diffstat (limited to 'chapter/4')
-rw-r--r--chapter/4/dist-langs.md47
1 files changed, 2 insertions, 45 deletions
diff --git a/chapter/4/dist-langs.md b/chapter/4/dist-langs.md
index 9f04232..1736064 100644
--- a/chapter/4/dist-langs.md
+++ b/chapter/4/dist-langs.md
@@ -1,53 +1,10 @@
---
layout: page
title: "Distributed Programming Languages"
-by: "A Systems Person"
+by: "Joe Schmoe and Mary Jane"
---
-### Two major major, orthogonal approaches to distributed languages:
-
-#### Actor / Object model
-
-The actor model has its roots in procedural programming.
-This model maps in a straighforward way to a distributed environment.
-
-* Erlang
-* Cloud Haskell (I know, right? Why?)
-
-#### Dataflow model (static and stream)
-
-The dataflow model has its roots in functional programming.
-Some languages that use this model are:
-
-* Multilisp
-* MapReduce (Spark, Hadoop, etc.)
-
-### Why GPL's not DSL's?
-
-* problem of domain-composition
-* problem of abstraction
-* problem of ecosystem
-* problem of tumultuous architecture
-* "any gpl + library can act as a dsl" - mernik"
-
-#### Erlang vs C: A Tar and Feathering
-
-{% cite Armstrong2010 --file dist-langs %}
-
-Erlang offers nothing that is unavailable in C.
-
-For example, dynamic code swapping is one of Erlang's major selling points.
-However, code swapping can easily be achieved in C with dynamic linking.
-This approach is analogous to the example offered in the Erlang paper.
-
-Other selling points, such as isolation, concurrency, and message passing can all be accomplished with unix-style system calls.
-Why is this language not considered redundant?
-
-#### MapReduce: A New Hope
-
-Unlike Erlang, MapReduce and DSL's that implement the paradigm are "all the rage."
-Unlike Erlang, MapReduce has experienced adoption because it offers true abstraction of the problems of distributed computing.
-Erlang only provided a way of detecting a process failure; it did not consider machine or network failures.
+Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. {% cite Uniqueness --file dist-langs %}
## References