Triple scripts are not intended subsume everything in the world. The triple script invariants practically ensure that there are many use cases to which triple scripts cannot be the solution. You will never be able to write a chat client as a triple script, for example, (nor could you write the chat server that the client communicates with as a triple script).
It is a triplescripts.org mantra that Triple scripts are for everyone, but not for all things.
There is an entire industry and multiple markets that are being served by "traditional" fixtures of computing. The triplescripts.org group was explicitly chartered to serve the people and use cases that are otherwise underserved (and overburdened) by the traditional way that software is developed.
If you want to write an app that can do something that is otherwise impossible while at the same time maintaining the triple script invariants, or it's impossible without going against the overall philosophy of the triple scripts ecosystem, then you should of course still write your app—just not as a triple script. Similarly, if you want to write your app in a different language, let's say Clojure, or Haskell, or Rust, or C++, or for NodeJS, particularly because that other language has something that the triple script dialect lacks, then you should probably use those languages. (But in each case, you should still consider using a triple script for your build tooling.)