(→Participating: reword greenfield comment) |
(→Introduction: update for July) |
||
Line 33: | Line 33: | ||
== Introduction == |
== Introduction == |
||
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]] |
* [[Build Manifesto]] |
Revision as of 18:13, 6 July 2020
This is the wiki for triplescripts.org — committed to software tooling 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.)
Participating
Why should you participate in triplescripts.org?:
- triplescripts.org cares about software longevity
- most accessible software stack in the world
- greenfield opportunities for building out the ecosystem
Who shouldn't participate in triplescripts.org?:
- people who think minification is an acceptable compromise
- people whose foremost concern is making the GitHub contribution graph light up green and their npm package rosters look full
- people who are enamored with the NodeJS and NPM ecosystems in general
Introduction
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