Content added Content deleted
(pull out "networked application" from "Who shouldn't participate[...]") |
m (Relocate "Triple scripts are for everyone[...]" blurb) |
||
| Line 15: | Line 15: | ||
* networked applications |
* networked applications |
||
| ⚫ | |||
== Participating == |
== Participating == |
||
| Line 28: | Line 30: | ||
* people whose foremost concern is making the GitHub contribution graph light up green and their npm package rosters look full |
* 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 |
* people who are enamored with the NodeJS and NPM ecosystems in general |
||
| ⚫ | |||
Revision as of 16:22, 17 June 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
Participating
Why should you participate in triplescripts.org?:
- triplescripts.org cares about software longevity
- most accessible software stack in the world
- greenfield module 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