Welcome: Difference between revisions

From triplescripts.org wiki
Content added Content deleted
No edit summary
(→‎Applications: traditional system software)
 
(23 intermediate revisions by 2 users not shown)
Line 1: Line 1:
__NOTOC__
__NOTOC__


This is the wiki for [https://triplescripts.org triplescripts.org] — committed to software tooling for the out-crowd.
This is the wiki for [https://triplescripts.org triplescripts.org] — committed to software tooling for the out-crowd. To learn more about triple scripts and the triple scripts ecosystem, check the existing material on triplescripts.org, have a look at [[the why and how of triple scripts]], or read on.


== Applications ==
== Applications ==
Line 10: Line 10:
* auditable, offline software security fobs
* auditable, offline software security fobs
* file format decompressors, explorers, manipulators, etc
* 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
* ... and other utilities that perform limited IO (particularly suited for one or more file inputs with zero or one file outputs, in the vein of programming language compilers or [[filters]])


What triple scripts are not suited for:
== Participating ==


* networked applications
Why should you participate in triplescripts.org?:
* applications for communicating with peripheral devices
* triplescripts.org cares about software longevity
* ... and many, many other classes of traditional system software
* most accessible software stack in the world
* greenfield module ecosystem


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


== More information ==
Who shouldn't participate in triplescripts.org?:
* people who want to work on networked applications
* 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


This wiki was started in June 2020, and at this time it remains fairly sparse. To get a clearer picture of what this is all <em>about</em>, you can find pertinent info on the following pages:
"Triple scripts are for everyone, but not for all things"

* [[ABCs of triple scripts]]
* [[Build Manifesto]]
* [[Gestalt of Smalltalk]]
* [[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 [https://triplescripts.org/invariants the triple script invariants]. Given their importance, we'll repeat them here: we say that '''triple scripts are'''...
* '''self-contained'''
* '''homologous'''
* '''automorphic'''

Latest revision as of 10:02, 5 December 2023


This is the wiki for triplescripts.org — committed to software tooling for the out-crowd. To learn more about triple scripts and the triple scripts ecosystem, check the existing material on triplescripts.org, have a look at the why and how of triple scripts, or read on.

Applications[edit]

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 IO (particularly suited for one or more file inputs with zero or one file outputs, in the vein of programming language compilers or filters)

What triple scripts are not suited for:

  • networked applications
  • applications for communicating with peripheral devices
  • ... and many, many other classes of traditional system software

Triple scripts are for everyone, but not for all things. (See other mantras.)

More information[edit]

This wiki was started in June 2020, and at this time it remains fairly sparse. To get a clearer picture of what this is all about, you can find pertinent info on the following pages:

... 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
Cookies help us deliver our services. By using our services, you agree to our use of cookies.