Toggle menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.


From wiki
Revision as of 13:13, 27 September 2023 by Colby Russell (talk | contribs) (de-emphasize job)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

With respect to group proposals to evolve the triple script dialect, proponents should keep in mind triple scripts were created to make people's lives easy. That includes not just the job of the person writing triple scripts, but also the compiler writers' life, and the experience of the person who has to read a triple script written by someone else.

From a language development standpoint, all the rules to translate a list of modules from pre-compilation form into the t-block–based triple script file format should be easy to keep in a person's head, and the process itself should be easy to accomplish by hand. We want to keep the dialect such that a programmer can start writing a new triple script by creating a new file and then begin directly writing what the compiler would output, without having to first create all modules as individual files and without requiring access to a compiler. Above all, the compiler's output should be predictable, with no surprises. This is only possible by avoiding as much as is reasonably possible any constructs that will come along with a set of corner cases that will have to be dealt with.

Rich Hickey contrasts simple versus easy. In the view of the's group and in light of its values, sometimes being easy trumps simplicity, and sometimes it doesn't; simplicity is not ipso facto better than easy, and easiest is not ipso facto better than easy.

See also[edit]

This is not JavaScript and other mantras

Cookies help us deliver our services. By using our services, you agree to our use of cookies.