Content added Content deleted
(fix typo and revise for clarity) |
(s/browser/universal application runtime/ and make it clear that you don't *have* to have a graphical form) |
||
| Line 1: | Line 1: | ||
<div class="hatnote" style="margin: 1em 2em;">''"system" redirects here; not to be confused with the [[SystemA]] pattern.''</div> |
<div class="hatnote" style="margin: 1em 2em;">''"system" redirects here; not to be confused with the [[SystemA]] pattern.''</div> |
||
Triple scripts are written to use parametric '''capabilities''', leading to programs written to target an '''abstract system interface''', rather than directly making use of platform-specific affordances exposed by the host environment. Note that it is this abstraction which is crucial to the [[homologous]] nature of triple scripts, allowing them to run both |
Triple scripts are written to use parametric '''capabilities''', leading to programs written to target an '''abstract system interface''', rather than directly making use of platform-specific affordances exposed by the host environment. Note that it is this abstraction which is crucial to the [[homologous]] nature of triple scripts, allowing them to run both in the [[universal application runtime]] (possibly even with a graphical UI, at the author's discretion) or directly in the terminal. |
||
== See also == |
== See also == |
||
Revision as of 18:36, 17 December 2020
"system" redirects here; not to be confused with the SystemA pattern.
Triple scripts are written to use parametric capabilities, leading to programs written to target an abstract system interface, rather than directly making use of platform-specific affordances exposed by the host environment. Note that it is this abstraction which is crucial to the homologous nature of triple scripts, allowing them to run both in the universal application runtime (possibly even with a graphical UI, at the author's discretion) or directly in the terminal.