Artifact Content
Not logged in

Artifact 65bf1999ccb8f72da5fed6a2582efb31639de957:

Wiki page [Application Example: Silktorrent Package Manager] by martin_vahi on 2016-08-02 22:23:55.
D 2016-08-02T22:23:55.113
L Application\sExample:\sSilktorrent\sPackage\sManager
P 5e567cf3dad1b9f7a4f9d148d52420672c03dbbc
U martin_vahi
W 2444
<h1 style="text-align: left;">The Core Idea</h1>

<p>If the silktorrent packet is a tar-file that contains folders&nbsp;</p>

<p><b>payload</b></p>

<p><b>header</b></p>

<p>then in software projects and HTML pages &nbsp;the content of the folders
<b>payload</b> and <b>header</b> can be referenced by using the
<a href="http://bitrary.softf1.com/index.php?title=Art_:_Source_Code#Tree_Encoding">tree
encoding</a>:</p>

<p><b>&lt;tar-file name&gt;/payload/&lt;the file or folder relative to the
folder payload&gt;</b></p>

<p><b>&lt;tar-file name&gt;/header/&lt;the file or folder relative to the
folder header&gt;</b><br>
</p>

<p>The&nbsp;&lt;tar-file name&gt; can be also the name of a local folder or
some folder at some publicly hosted web page. The include/require/src/uses
statements of various programming languages and configurations files, including
HTML, can be modified by changing the prefix of the &lt;tar-file name&gt;. That
allows an HTML-page to be switched from using JavaScript libraries from one
site to using the very same JavaScript libraries from another site.</p>

<p><b>http://www.first_site.com/</b>&lt;tar-file name&gt;/payload/the_JavaScript_library.js<br>
</p>

<p><b>http://www.second_site.com/</b>&lt;tar-file name&gt;/payload/the_JavaScript_library.js<br>
</p>

<p>Due to the possibility to use regular expressions, the proposed solution
does not require code generation. It might be usable with many existing IDE-s
without requiring any additional tools or plugins. The solution is also
programming language agnostic.</p>

<p><br>
</p>

<h1>Theory</h1>

<div>The Core Idea has an assumption that <b>backwards compatibility of
libraries does not exist, even if advertised</b>. Whenever a software component
dependency is declared by stating that the version of the dependency is
"newest" or "greater than X", a flaw is introduced. That is the reason, why
Linux/BSD/etc. package collections are "unstable" and NEVER WILL BE "stable".
For built/compiled software components <b>each combination of build parameters,
compiler, environment set-up is actually a separate version of the software
component</b>.&nbsp;</div>

<div><br>
</div>

<div><br>
</div>

<h1>Partial list of Similar Software</h1>

<div>
<ul>
<li><a href="http://www.toastball.net/toast/">toast</a> <i>(<a href="https://archive.is/uIRaz">archival
copy</a>, <a href="./ainfo/a99d7f95d0d8255e">source code</a>)</i></li>
</ul></div>

<div><br>
</div>

Z 29660f7eea62d734153890bc0951c56e