Hi Talha, Our browser-based astronomical image display (https://js9.si.edu) is transformed into a full desktop app using Electron and a few hundred lines of wrapper code. Having the same code base for both environments is a huge benefit. We also very cautiously allow use of Electron's node capabilities to make the underlying file system available on the desktop app.The main drawback for us (compared to a pure desktop app using Aqua or X11) is lack of mmap() and the limit on the amount of available memory: our files are large (> 100Mb) or even huge (> 1Gb) and special techniques are required to cut down on memory use.
We use Emscripten to compile cpu-intensive astronomical i/o, reprojection, and world coordinate system libraries to wasm. Although the results run at near-native speed thanks to Emscripten, our data processing takes much more time than an ordinary web app. As a result, we probably don't notice Electron-specific inefficiencies that others might. Regards, Eric -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/7017d53b-c824-4ea3-a5f8-1e6c941f48b6%40googlegroups.com.
