remarkable VS sciter-js-sdk

> we can't take some well-tested, used-by-millions library

You can.

Here is an example of Sciter application that uses RemarkableJS library (https://github.com/jonschlinkert/remarkable) as it is:

https://quark.sciter.com/quark-application-samples/hello-mar...

Simultaneously the #1 trending developer on GitHub across all languages (out of ~17 million developers at the time) with multiple #1 trending projects: Remarkable (https://github.com/jonschlinkert/remarkable), a markdown parser and compiler (also across all languages, out of ~7 million projects), Enquirer (https://github.com/enquirer/enquirer), a stylish, user-friendly prompt system.

Since then they've made things that are IMO quite useful, like enquirer, micromatch, and remarkable.

mdview (sources) uses RemarkableJS for MD->HTML conversion.

will give you split-view out-of-the-box. But web dev's will start looking for frameworks in order to achieve this simple task that browser have internally already.

TL;DR: Web and desktop UIs use inherently different models. You can share parts between these two different platforms but only parts, really.

[1] Remarkable JS: https://github.com/jonschlinkert/remarkable

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.

Check this example of native object: https://github.com/c-smile/sciter-js-sdk/blob/main/demos/int...

So you really don't need V8 JIT infrastructure to achieve max performance - just add native objects when needed.

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

React works with some modifications: check https://github.com/c-smile/sciter-js-sdk/blob/main/samples/r...

VueJS works as it is.

Surprisingly, these are enough to allow to use pretty much all ReactJS functionality, and with native speed. And without the need for any external libraries. Check: https://github.com/c-smile/sciter-js-sdk/tree/main/docs/md/r...

For C++ you might try https://github.com/c-smile/sciter-js-sdk, basically an Electron-Replacement without all the Node baggage (the binary lib is just some MB in size). It can also be easily mixed with other Win32-Controls as it is itself a self-painting Win32-Control. Checkout the numerous demos.

Then, the Sciter dynamic link library must be in the same folder as heatmap.exe for it to run.