# HG changeset patch
# User František Kučera <franta-hg@frantovo.cz>
# Date 1547242745 -3600
# Node ID ea49ee7a73c91eb7fc3922aafe43175cfebb1198
# Parent  ee2f682259c2dfccfdb96f53a0bc3e0e31aae3fb
principles: Optional complexity

diff -r ee2f682259c2 -r ea49ee7a73c9 relpipe-data/principles.xml
--- a/relpipe-data/principles.xml	Fri Jan 11 18:09:50 2019 +0100
+++ b/relpipe-data/principles.xml	Fri Jan 11 22:39:05 2019 +0100
@@ -103,6 +103,23 @@
 			-->
 		</p>
 		
+		<h2>Optional complexity</h2>
+		
+		<p>
+			We are not scared by things like XML, SQL, Java or even C++ and we do not hate them.
+			There are use cases where their complexity is reasonable and makes sense.
+			But on the other hand, there are many scenarios, where such complexity is not necessary or is even harmful.
+			This leads us to the conclusion: <em>the complexity must be optional</em>.
+		</p>
+		<p>
+			Thus <m:name/> data format is independent of above-mentioned <em>complex</em> technologies
+			and our implementation is divided into many separate modules (tools).
+			So the user could download, compile and run only the parts he really needs.
+		</p>
+		<p>
+			<m:name/> can serve as a <em>bridge</em> between the <em>complex world</em> and the <em>simple world</em>.
+		</p>
+		
 		
 		<h2>Sane dependencies</h2>