aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDimitri Staessens <dimitri@ouroboros.rocks>2020-04-28 20:58:40 +0200
committerDimitri Staessens <dimitri@ouroboros.rocks>2020-04-28 20:58:40 +0200
commit7339549721fb1b54a0abd47502e4f1fae2c48093 (patch)
tree9bb44d40ecf43b0fb16a460f29accb159dcce54d
parentf38dfd2db111a2095aa29b959701d74a737de474 (diff)
downloadwebsite-7339549721fb1b54a0abd47502e4f1fae2c48093.tar.gz
website-7339549721fb1b54a0abd47502e4f1fae2c48093.zip
content: Remove bashing of current layered model
-rw-r--r--content/en/docs/Overview/_index.md7
1 files changed, 0 insertions, 7 deletions
diff --git a/content/en/docs/Overview/_index.md b/content/en/docs/Overview/_index.md
index 019e839..fe5e36c 100644
--- a/content/en/docs/Overview/_index.md
+++ b/content/en/docs/Overview/_index.md
@@ -17,13 +17,6 @@ interfaces into inter-operate with common technologies: run Ouroboros
over Ethernet or UDP, or create tunnels over Ouroboros using tap or
tun devices.
-Why? Because we think there are fundamental problems with the current
-model (referred to as the 4-Layer, 5-Layer or 7-Layer model --
-depending on who you ask). This problem is self-evident: a crippling
-lack of abstraction and a complete disregard for elegance that results
-in a technology that _works_ but can at best be described as an overly
-complicated mess.
-
From an application perspective, Ouroboros network operates as a "black
box" with a
[very simple interface](https://ouroboros.rocks/man/man3/flow_alloc.3.html).