Welcome: Difference between revisions

From triplescripts.org wiki
Content added Content deleted
(list some pages and concepts as an intro to the wiki content)
Line 16: Line 16:
* networked applications
* networked applications


<q>''Triple scripts are for everyone, but not for all things''</q>
<q>''Triple scripts are for everyone, but not for all things''</q>. (See other [[mantras]].)


== Participating ==
== Participating ==

Revision as of 17:56, 18 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. (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 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

Pages

As of June 2020, the wiki is quite sparse. Here are some links to pertinent pages:

For those completely unacquainted with triple scripts and triple script development, please pay special attention to the triple script invariants. Given their important, we'll repeat them here by saying triple scripts are:

  • self-contained
  • homologous
  • automorphic
Cookies help us deliver our services. By using our services, you agree to our use of cookies.