This page has source licensing prices for Win/Mac/Linux, maybe they changed the license? https://sciter.com/prices/
From https://www.codeproject.com/Articles/33662/TIScript-language..., "The design of TIScript was based on the analysis of practical JavaScript use cases. In some areas, it simplifies and harmonizes JavaScript features. For example, the prototype mechanism was simplified. In other cases, it extends JavaScript, while preserving the original "look-and-feel" of JS."
The history at https://sciter.com/10-years-road-to-sciter describes the path from C++, Java, D, Ruby, Python, Lua and JavaScript to TIScript and W3C contributions by the author. Web site says that Sciter (licensed or OSS?) and TIScript run on 270 millions PCs and Macs, as a UI component in AV products. On the topic of garbage collection:
"... each part of UI framework shall use its own memory management and ownership principles that are optimal for the role they are playing. HTML DOM tree has very regular structure with clear one parent – many children ownership graph. Life cycle of DOM elements (read “UI elements”) is also quite deterministic. There is absolutely no need for GC if to speak about HTML/CSS. But code-behind-UI – code that does UI automation in “on-click-here-push-item-there-and-collapse-panel-over-there” fashion has to be manageable. GC there is the must – ownership graph is unknown upfront and frequently contains loops."
From https://www.codeproject.com/Articles/33662/TIScript-language..., "The design of TIScript was based on the analysis of practical JavaScript use cases. In some areas, it simplifies and harmonizes JavaScript features. For example, the prototype mechanism was simplified. In other cases, it extends JavaScript, while preserving the original "look-and-feel" of JS."
The history at https://sciter.com/10-years-road-to-sciter describes the path from C++, Java, D, Ruby, Python, Lua and JavaScript to TIScript and W3C contributions by the author. Web site says that Sciter (licensed or OSS?) and TIScript run on 270 millions PCs and Macs, as a UI component in AV products. On the topic of garbage collection:
"... each part of UI framework shall use its own memory management and ownership principles that are optimal for the role they are playing. HTML DOM tree has very regular structure with clear one parent – many children ownership graph. Life cycle of DOM elements (read “UI elements”) is also quite deterministic. There is absolutely no need for GC if to speak about HTML/CSS. But code-behind-UI – code that does UI automation in “on-click-here-push-item-there-and-collapse-panel-over-there” fashion has to be manageable. GC there is the must – ownership graph is unknown upfront and frequently contains loops."