Toolbench pattern

If unhappy with a triple script, anyone has the opportunity to change it, but if they are unhappy with the restrictions of triple scripts in general (see invariants), they are encouraged to create their own "little shell" for the script.

Triple scripts can't make network requests, for example, so they're less capable in that regard than even an ordinary web page. But there's nothing stopping anyone from creating a small app that includes its own triple script runtime and which takes as input a given triple script and then cooperatively drives it in a way that is felt to be more "ergonomic".

Consider UNIX. If something bothers you about curl, you have the option of patching it to do what you want. But suppose there were an impedance mismatch that you feel when you use curl, but curl itself is doing the job it's supposed to do and following ordinary conventions. Consider whether the problem you're feeling is one of ergonomics—might it be possible to make special-purpose changes to your shell that would resolve the issue? Shells' scripting and configuration options notwithstanding, deep changes and integration at this level is not normally seen on UNIX, because the traditional implementation language (C) has subtle and not-so-subtle effects on the mealleability of the system.