equal
deleted
inserted
replaced
101 <!-- |
101 <!-- |
102 Thus implementing the relational output to an existing program should be matter of few hours. |
102 Thus implementing the relational output to an existing program should be matter of few hours. |
103 --> |
103 --> |
104 </p> |
104 </p> |
105 |
105 |
|
106 <h2>Optional complexity</h2> |
|
107 |
|
108 <p> |
|
109 We are not scared by things like XML, SQL, Java or even C++ and we do not hate them. |
|
110 There are use cases where their complexity is reasonable and makes sense. |
|
111 But on the other hand, there are many scenarios, where such complexity is not necessary or is even harmful. |
|
112 This leads us to the conclusion: <em>the complexity must be optional</em>. |
|
113 </p> |
|
114 <p> |
|
115 Thus <m:name/> data format is independent of above-mentioned <em>complex</em> technologies |
|
116 and our implementation is divided into many separate modules (tools). |
|
117 So the user could download, compile and run only the parts he really needs. |
|
118 </p> |
|
119 <p> |
|
120 <m:name/> can serve as a <em>bridge</em> between the <em>complex world</em> and the <em>simple world</em>. |
|
121 </p> |
|
122 |
106 |
123 |
107 <h2>Sane dependencies</h2> |
124 <h2>Sane dependencies</h2> |
108 |
125 |
109 <p> |
126 <p> |
110 The libraries and the tools should not depend on any libraries other than the standard library of given programming language. |
127 The libraries and the tools should not depend on any libraries other than the standard library of given programming language. |