146 <ul> |
146 <ul> |
147 <li>Shell – we use existing shells (e.g. GNU Bash), work with any shell and even without a shell (e.g. as a stream format passed through a network or stored in a file).</li> |
147 <li>Shell – we use existing shells (e.g. GNU Bash), work with any shell and even without a shell (e.g. as a stream format passed through a network or stored in a file).</li> |
148 <li>Terminal emulator – same as with shells, we use existing terminals and we can use <m:name/> also outside any terminal; if we interact with the terminal, we use standard means like Unicode, ANSI escape sequences etc.</li> |
148 <li>Terminal emulator – same as with shells, we use existing terminals and we can use <m:name/> also outside any terminal; if we interact with the terminal, we use standard means like Unicode, ANSI escape sequences etc.</li> |
149 <li>IDE – we can use standard <m:unix/> tools as an IDE (GNU Screen, Emacs, Make etc.) or any other IDE.</li> |
149 <li>IDE – we can use standard <m:unix/> tools as an IDE (GNU Screen, Emacs, Make etc.) or any other IDE.</li> |
150 <li>Programming language – <m:name/> are language-independent data format and can be produced or consumed in any programming language.</li> |
150 <li>Programming language – <m:name/> are language-independent data format and can be produced or consumed in any programming language.</li> |
151 <li>Query language – although some of our tools are doing queries, filtering or transformations, we are not inventing a new query language – instead, we use existing languages like SQL, XPath or regular expressions.</li> |
151 <li>Query language – although some of our tools are doing queries, filtering or transformations, we are not inventing a new query language – instead, we use existing languages like SQL, XPath, Guile/Scheme, AWK or regular expressions.</li> |
152 <!--<li>Text editor – </li>--> |
152 <!--<li>Text editor – </li>--> |
153 <li>Database system, DBMS – we focus on the stream processing rather than data storage. Although sometimes it makes sense to redirect data to a file and continue with the processing later.</li> |
153 <li>Database system, DBMS – we focus on the stream processing rather than data storage. Although sometimes it makes sense to redirect data to a file and continue with the processing later.</li> |
154 </ul> |
154 </ul> |
155 |
155 |
156 |
156 |
163 <p> |
163 <p> |
164 On the other hand, the already published tools (tagged as v0.x in v_0 branch) should work quite well (should compile, should run, should not segfault often, should not wipe your hard drive or kill your cat), |
164 On the other hand, the already published tools (tagged as v0.x in v_0 branch) should work quite well (should compile, should run, should not segfault often, should not wipe your hard drive or kill your cat), |
165 so they might be useful for someone who likes our ideas and who is prepared to update own programs and scripts when the new version is ready. |
165 so they might be useful for someone who likes our ideas and who is prepared to update own programs and scripts when the new version is ready. |
166 </p> |
166 </p> |
167 |
167 |
168 <p>We also promise to fulfill all requirements of the Sane software manifesto before we release the version 1.0:</p> |
168 <p>We promise to fulfill all requirements of the Sane software manifesto before we release the version 1.0:</p> |
169 <p style="text-align: right"> |
169 <p style="text-align: right"> |
170 <a href="https://sane-software.globalcode.info/"> |
170 <a href="https://sane-software.globalcode.info/"> |
171 <img alt="Sane software manifesto" src="img/sane-software-logo-rectangle.png"/> |
171 <img alt="Sane software manifesto" src="img/sane-software-logo-rectangle.png"/> |
172 </a> |
172 </a> |
173 </p> |
173 </p> |