To both the_duke and sfink, as one who did both embeddings, there were multiple issues during multi-prong integration efforts: Each has their own challenges ba

To both the_duke and sfink, as one who did both embeddings, there were multiple issues during multi-prong integration efforts: Each has their own challenges based on various JavaScript bytecode detection algorithms (as well as disparate JS engine design) and its varied requirements on the multiplexing of selected external stimuli that it requires. As a result, after placements of many instrumentation points were inserted throughout both browsers and many custom JS engines based on various detection researches, there are needs to have multiple but separate executables having one or more combination of the following: - custom ES6 pre-loading, - Rendered layout memory access - DOM shadowing - selectable UI external stimuli (event, drag) - variable wall-clock timescale compression/expansion - translated memory access And that belies my next project, centralization and merger of all these many executables. Various desired functionalities got dropped in the code by Mozilla and Google devs so code reduction/refactoring were done over time for those. That’s about as detailed as I can put forth.