Content added Content deleted
(→Participating: relocating section to triplescripts.org wiki:About) |
|||
Line 18: | Line 18: | ||
<q>''Triple scripts are for everyone, but not for all things''</q>. (See other [[mantras]].) |
<q>''Triple scripts are for everyone, but not for all things''</q>. (See other [[mantras]].) |
||
== |
== More information == |
||
This wiki was started in June 2020, and at this time it remains fairly sparse. Seek info from some of the following pertinent pages: |
This wiki was started in June 2020, and at this time it remains fairly sparse. Seek info from some of the following pertinent pages: |
Revision as of 01:05, 13 July 2020
This is the wiki for triplescripts.org — committed to software tools for the out-crowd.
Applications
What triple scripts are well-suited for:
- portable, no-fuss build scripts
- auditable, offline software security fobs
- file format decompressors, explorers, manipulators, etc
- ... and other utilities that perform limited file IO; particularly suited for many file inputs, zero or one file outputs
What triple scripts are not suited for:
- networked applications
Triple scripts are for everyone, but not for all things
. (See other mantras.)
More information
This wiki was started in June 2020, and at this time it remains fairly sparse. Seek info from some of the following pertinent pages:
- Build Manifesto
- Gestalt of Smalltalk
- Selective reification
- This is not JavaScript
- Dialect
- SDIPD
- File format
... and other terms listed in the glossary.
For those completely unacquainted with triple scripts and triple script development, please pay special attention to the triple script invariants. Given their importance, we'll repeat them here: we say that triple scripts are...
- self-contained
- homologous
- automorphic