genetic-origins-heatmap VS sciter-js-sdk

When I write a program I usually make it focused on a single thing that it's supposed to accomplish. For example, Calligrapher AI lets you type text and then "writes" the same text in human-like handwriting while you watch, and lets you save the image. Beep Knobs is just a board with knobs (albeit a fancy one) that lets you generate customized beeps. And Genetic Origins Heatmap does just what it sounds like, produces a world map indicating where your ancestors came from (using 23andMe DNA data, for example).

Here is an application I wrote that works the same, but is simpler to use. Currently it only accepts 23andMe data but I intend to update it to support AncestryDNA also. I will edit this comment when it's done.

There's an additional flaw that I realize only in retrospect: A naïve heatmap will tend to exaggerate the significance of regions for which there are more datapoints, since they overlap and contribute to raising the temperature for that particular cluster. But this is a minor issue that doesn't fully explain the Switzerland thing. If any programmers would like to help resolve this, here is the source code on Github.

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) {