You asked me how to avoid the overhead of Electron and I suggested you try αcτµαlly pδrταblε εxεcµταblε since the distributables are 10,000x smaller. If it's not possible to meet your requirements using a command line c program, or a web application that runs in the browser, then could you help me understand why you need electron?
I'm not advocating for Electron... I think either you're misunderstanding me or we're misunderstanding each other (quite possible as well).
I'm advocating for some small cross-platform cross-language API / runtime / framework (not sure what it looks like, but since most languages are targetting WASM (if this is what's making you think I'm advocating for Electron... then you missed my commentary about people making stand alone WASM runtimes) as opposed to solutions that are platform or language specific, and when I say platform specific lump in web (which means Electron too) in that bucket.
What most people want is to be able to use their own preferred language and do a UI without having to import a bunch of C or C++ libraries that will add additional overhead over their language.
Edit: Just saw the post you were referring to, it would of made more sense had you linked to it:
While this answers the 1 binary problem while producing a rather massive executable file larger than Electron in many cases, this still doesn't solve the problem I'm mentioning: We need a cross-platform cross-language UI solution. If you want to do away with things like Electron, you need to consider all platforms and all languages.
