Quote Originally Posted by DavidXanatos View Post
Assuming that QJSEngine may become an implemetation detail of QQml and QScriptEngine will stay for application scripting, it may be an interesting option to create a fork of the current v8 based QJSEngine with an exposed debug interface for in app debugging, and those use cases where a lot of JS performance is needed and the slow interface for QObject is not significant.
Nothing can stop you from extracting QJSEngine code, renaming it to QV8Engine and making it a separate library.

But you are probably right that Qt wont maintain 2 scripting engines that basically do almost the same, just with different performance and platform compatibility.

So if there is a need for such a thing it would have to be some extern component maintained by some 3rd party.
I would assume the Trolls will want V4 to be as fast as V8. Since it's JIT, execution speed (of the compiled code at least) should be similar.