"a faster engine like V8" It is actually not the fact that V8 in context of Sciter alike use cases will be faster. Consider this statement: document.body

"a faster engine like V8" It is actually not the fact that V8 in context of Sciter alike use cases will be faster. Consider this statement: document.body.patch(<body>Hello world</body>); In case of Sciter this expression runs with native speed. JSX is built-in and element.patch() method is native. While in browser, in case of ReactJS, you will run that patch() (reconciliation procedure ReactDOM.render) with JS VM speed as that algorithm is implemented on JS/TS. The whole point of Sciter is in its embeddability - you can add native objects of your app callable directly from script. Check this example of native object: https://github.com/c-smile/sciter-js-sdk/blob/main/demos/integration/frame.cpp#L8 https://github.com/c-smile/sciter-js-sdk/blob/main/demos/int... So you really don't need V8 JIT infrastructure to achieve max performance - just add native objects when needed.