> Once VLC.js runs, you can reasonably expect it to run forever You can reasonably expect it to run... until the first non-backward compatible change in anythi

> Once VLC.js runs, you can reasonably expect it to run forever You can reasonably expect it to run... until the first non-backward compatible change in anything the code depends on. The major assumption for this to keep working is that everything has to be permanently kept up-to-date for all the breaking dependencies. And I assume it will always be easier to produce a Linux or Windows binary that works relatively long without changes than anything that non-trivially depends on the web technologies. A few years ago, as far as I know, it was still possible to run the Netscape Navigator binary which was around 20 years old on the recent Linux kernel.