relpipe-data/index.xml
branchv_0
changeset 145 42bbbccd87f3
parent 144 ee7e96151673
child 146 8c2e2dbee5cc
equal deleted inserted replaced
144:ee7e96151673 145:42bbbccd87f3
   116 			So <m:name/> are not a:
   116 			So <m:name/> are not a:
   117 		</p>
   117 		</p>
   118 		
   118 		
   119 		<ul>
   119 		<ul>
   120 			<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>
   120 			<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>
   121 			<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 as Unicode, ANSI escape sequences etc.</li>
   121 			<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>
   122 			<li>IDE – we can use standard <m:unix/> tools as an IDE (GNU Screen, Make etc.) or any other IDE.</li>
   122 			<li>IDE – we can use standard <m:unix/> tools as an IDE (GNU Screen, Make etc.) or any other IDE.</li>
   123 			<li>Programming language – <m:name/> are language-independent data format and can be produced or consumed in any programming language.</li>
   123 			<li>Programming language – <m:name/> are language-independent data format and can be produced or consumed in any programming language.</li>
   124 			<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>
   124 			<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>
   125 			<!--<li>Text editor – </li>-->
   125 			<!--<li>Text editor – </li>-->
   126 			<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>
   126 			<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>
   129 		
   129 		
   130 		<h2>Project status</h2>
   130 		<h2>Project status</h2>
   131 		
   131 		
   132 		<p>
   132 		<p>
   133 			The main ideas and the roadmap are quite clear, but many things will change (including the format internals and interfaces of the libraries and tools).
   133 			The main ideas and the roadmap are quite clear, but many things will change (including the format internals and interfaces of the libraries and tools).
   134 			Because we know how important the API and ABI stability is, we are not ready to publish the version 1.0 yet.
   134 			Because we understand how important the API and ABI stability is, we are not ready to publish the version 1.0 yet.
   135 		</p>
   135 		</p>
   136 		<p>
   136 		<p>
   137 			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),
   137 			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),
   138 			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.
   138 			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.
   139 		</p>
   139 		</p>