(Created page with "Triple scripts are an embodiment of the '''SDIPD''' principle (pronounced "serendipity" or "s'dipity"?). SDIPD stands for "package distribution is source distribution [''sic'...") |
(better explanation + "non-destructive compilation") |
||
| Line 1: | Line 1: | ||
Triple scripts are an embodiment of the '''SDIPD''' principle (pronounced "serendipity" or "s'dipity"?). SDIPD stands for "package distribution is source distribution [''sic'']". (Yes, really. Equality is commutative.) |
Triple scripts are an embodiment of the '''SDIPD''' principle (pronounced "serendipity" or "s'dipity"?). SDIPD stands for "package distribution is source distribution [''sic'']". (Yes, really. Equality is commutative.) |
||
Software that obeys the SDIPD principle eschews with traditional toolchains, requiring instead '''non-destructive compilation''' (if any compilation occurs at all). Traditional compilers take as input human readable source code and mangle it to produce an executable from which the original source code cannot be recovered. (In the 1980s, this implementation detail catalyzed the free software movement, later rebranded as "open source" with the release of the Netscape Navigator source code in 1998.) With non-destructive compilation, the executable produced by the compiler can be considered equivalent to the original source code from which it was created because it is possible reverse the compilation process to reproduce the original source code with perfect fidelity. |
|||
Among other properties that triple scripts exhibit, the triple script file format was designed to respect SDIPD. The triplescripts.org reference compiler [[trplkt]] uses non-destructive compilation. (The obvious question is whether trplkt itself exhibits SDIPD, and the answer is "yes"; trplkt is itself implemented as a triple script.) |
|||
== See also == |
== See also == |
||
Revision as of 00:03, 20 August 2020
Triple scripts are an embodiment of the SDIPD principle (pronounced "serendipity" or "s'dipity"?). SDIPD stands for "package distribution is source distribution [sic]". (Yes, really. Equality is commutative.)
Software that obeys the SDIPD principle eschews with traditional toolchains, requiring instead non-destructive compilation (if any compilation occurs at all). Traditional compilers take as input human readable source code and mangle it to produce an executable from which the original source code cannot be recovered. (In the 1980s, this implementation detail catalyzed the free software movement, later rebranded as "open source" with the release of the Netscape Navigator source code in 1998.) With non-destructive compilation, the executable produced by the compiler can be considered equivalent to the original source code from which it was created because it is possible reverse the compilation process to reproduce the original source code with perfect fidelity.
Among other properties that triple scripts exhibit, the triple script file format was designed to respect SDIPD. The triplescripts.org reference compiler trplkt uses non-destructive compilation. (The obvious question is whether trplkt itself exhibits SDIPD, and the answer is "yes"; trplkt is itself implemented as a triple script.)