Easy

With respect to group proposals to evolve the triple script dialect, proponents should keep in mind triple scripts were created to make people's jobs easy. That includes the compiler writers' jobs, the job of the person writing triple scripts, and the job 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 opening up a single file and then begin directly writing what would be the out.app.htm file, without having to first create all modules as individual files and without 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.

It's possible that you're a programmer accustomed to doing things a certain way or getting certain returns from your bargain with society, and triplescripts.org doesn't jibe, so you seek to change that. Consider, though, that triple scripts may not be meant to be a solution for the problem you have in mind.

Rich Hickey contrasts simple versus easy. In the view of the triplescripts.org'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.