> and requires its interpreter (JVM) to be present on the machine.
That's hardly a drawback. If every Electron app can get away with shipping a Chromium instance with every installer, you can ship a JVM with your app.
That's hardly a drawback. If every Electron app can get away with shipping a Chromium instance with every installer, you can ship a JVM with your app.
Of course, it's not an either-or - I'm sure many of those containers would have Electron inside...
I have a Stack Overflow question at https://stackoverflow.com/q/8913543/303363 which taught me how to identify the right version of the runtime library and how to fetch it. I don't do software development for Windows in C++ these days but once in a while I do look back at this question to fondly remember the days of C++ programming on Windows.
Except for the tiny "SideBySide" glitch (which was quite confusing at first), software development with C++ on Windows using Visual Studio as the IDE was a pleasant experience. Backward compatibility was (probably still is?) a strong suit of Windows. A software written in the 1990s worked fine all the way up to 2015 or so, often with no changes or no recompile/rebuild required. The binaries and DLLs would just work fine without issues on newer versions of Windows as long as the CRT the software was built with is also packaged in the software distribution.