clipper VS sciter-js-sdk

I've performed a couple experiments remaking Electron apps using Sciter.

My first target was https://github.com/AkashRajpurohit/clipper, a neat little clipboard manager. The owner was gratious enough to officially list my project under the "Clones" section of his readme =D The result was a 6mb file, compared to the original 165mb Electron app.

The second attempt was https://github.com/girkovarpa/temps-lite, an aesthetically-pleasing weather app which was motivated largely by the fact that the original was broken and abandoned yet still had people who wanted to use it. According to the open issues and forks trying to resurrect it, anyway. The file size savings were similar to the former, and they start virtually instantly. The Electron apps have a bit of delay and then a blank window before they finish starting up.

How tiny is the output? What is the API? (I couldn't find any documentation. I thought maybe it's in the Help menu in the app itself but all I found was this https://i.imgur.com/6puOMIe.png - On that note, what level of JS is supported? As far as I can tell it uses this https://github.com/c-smile/sciter-js-sdk which is based on Fabrice Bellard's QuickJS ) Is there sound?

JavaScript & Electron Sciter!

Having normal procedural language for build automation is of course useful. That's for those 10% of cases when "standard" build DSL (make,CMake,etc.) simply do not have facilities.

But the rest of 90% tasks should have compact (easily readable) definitions.

I personally found that Premake5 has quite good balance for these tasks.

Premake files are plain .lua files and due to Lua syntax they are easily readable. And if needed you can call from them procedures defined in again Lua.

So typical project (multiplatform) definition looks pretty readable, for example one project from Sciter SDK:

https://github.com/c-smile/sciter-js-sdk/blob/main/premake5....

More details.

That's why in Sciter I've extended JSX with translation meta instruction @:

Note Tauri is full fledged Client/Server with WebView (client) is running in separate process with RPC between UI process and Rust code (Server).

For the comparison:

Standalone Sciter (scapp.exe, https://github.com/c-smile/sciter-js-sdk/tree/main/bin) takes ~8 MB of RAM (with minimal Cairo and GDI backends).

That's 20 times less than even Tauri.

WebView based solutions are not suitable for applets - small portable desktop applications.

scapp.exe ( Standalone sciter engine ) takes 45 Mb showing its default "about" document.

It does support , with limited support but still.

See: https://github.com/c-smile/sciter-js-sdk/tree/main/samples/c...

Sciter also supports immediate mode painting on any element (like in DearIMGUI):

    element.paintBackground = function(gfx) {