Integration

Triple scripts can run in the browser today, by design. (And, of course, from the terminal using NodeJS—provided that's the command-line environment the author targets by including the necessary support modules; all triplescripts.org work so far has focused almost exclusively on NodeJS during the proofing stage, for pragmatic reasons.)

VSCode
VSCode alone cannot run "raw" triple script bundles like the browser *or NodeJS) can, but it's within the realm of possibility that a developer could provide an extension derived from their triple script. It's highly desirable, especially for the Build Manifesto that in the future this change—so that VSCode gain the ability to run arbitrary raw bundles, e.g. simply by pointing at one.  This should be possible using an extension, but there has been no work on this so far.

Ideal VSCode integration could use selective reification to provide optional inspectors, etc.

It's just as likely, whether intentional or not, that the VSCode team (or the wider developer community) ends up embracing and extending triplescripts.org's initiatives and effectively salts the ground for us, however...

Gnome Shell
Gnome ships with the ability to run JS apps today. In fact, Gnome Shell itself is written in JS.

GJS is also a candidate for a system backend as an alternative to NodeJS, as well as an an alternative to the browser (using embedded WebKit). There has been very little experimentation on a "SystemG" so far; we've opted to focus on NodeJS up until now, for stability. The best course of action for work on SystemG at this point would be to focus on Gnome as shipped with Ubuntu 20.04 LTS.

Further integration

 * Greasemonkey NG and the revival of Mozilla Labs's Ubiquity
 * Thunderbird - to replace the ailing XPI add-on system
 * sepsis-inspector - even though sepsis-inspector is essentially dead, it's still provides ground for experimentation, and we can always do a reboot built on Safari's WebInspector, but powered by mirrors and triple scripts (using selective reification)