XXX no matter what, really underscore that the triple script dialect is a targeted language; it's meant for writing a specific kind of program: build scripts and other meta tools. It's suitable enough that it can be used to write other kinds of programs in the same dialect, but it's not necessarily the goal. If people don't like it and want to write their compiler or other program some other like (like in JS—or literally anything else, although triple scripts are natively capable of acting as a "host" to a JS program), then that's what they should do—and not have any expectation that a rally to make the language fit for more general purpose use will be successful. See NOT#not-for-all-things.
- "Getting a development environment set up can be fast and easy"
- "Web apps have *not* solved the software distribution problem" (Wait, where's the pitch? Do triple scripts solve this problem? Answer: No.)
- "Expand your circle of collaborators to include all your users, too—and not just those with a technical affinity"
- "Because the world needs an ALGOL for 2020" (also helps in communicating what triple scripts are NOT)
- "The time for smart documentation is now"
- "SDIPD means free software" from a SDIPD for free software advocates, e.g. <https://github.com/alyssarosenzweig>. (See <https://github.com/alyssarosenzweig/carbon>.) See also <http://jordi.inversethought.com/blog/exercising-software-freedom-on-firefox/>
- We can draw parallels to the "buy it for life" movement; open source projects that adopt the triple scripts philosophy for their metatooling brings us much closer to being able to "buy" them for life
- Further reading:
- "This Page is Designed to Last" <https://jeffhuang.com/designed_to_last/>
- Software should be designed to last <https://jeffhuang.com/designed_to_last/>
- See also the Sandstorm manifesto <https://sandstorm.io/news/2014-07-21-open-source-web-apps-require-federated-hosting>, although there's an overemphasis on web apps there, whereas the focus of triple scripts is in a way very anti-web, even though it targets the browser runtime for its baseline platform.
- Even though "buy" is used metaphorically, there are certain implications of the triple scripts approach that make it friendly towards commercial open source—at least from a matter of perception regarding the kind of peace of mind people seek from things they pay money for
- Further reading:
- Ripped off from <https://ruben.verborgh.org/blog/2019/06/17/shaping-linked-data-apps/>: triplescripts.org brings a new way of building software in the open; rather than expecting your collaborators to download, configure, and/or familiarize themselves with a busy ecosystem of external tools, projects that adopt triple scripts make sure to give their collaborators the tools they need to start working immediately. For prospective contributors to a project, getting a development environment set up can be fast and easy.
- The repo is the IDE
- The Linux kernel's MAINTAINERS file documents the collaboration model in 19,000 lines. Other projects embed a screenshot or two to entice visitors, and these can weigh in at 500+KiB. At 19,000 lines or 500KiB, your project could include a capable build toolchain (compiler included). So stop asking your collaborators to go through the trouble of setting up fickle tooling that may or may not work as expected—just *give* them the right tools for the job.