Check this: https://sciter.com/wp-content/uploads/2020/06/ide.png https://sciter.com/wp-content/uploads/2020/06/ide.png that one has menu, check menu.htm in th

Check this: https://sciter.com/wp-content/uploads/2020/06/ide.png https://sciter.com/wp-content/uploads/2020/06/ide.png that one has menu, check menu.htm in that sample: https://github.com/c-smile/sciter-sdk/tree/master/samples/ideas/ide https://github.com/c-smile/sciter-sdk/tree/master/samples/id... > So can you run the benchmark suite with Sciter or not? Yes, I may do that but purpose is not clear. Their compiled C versions in Sciter will run definitely faster. These functions have nothing with UI per se. Yet, you can extend Sciter with native DirectX or OpenGL code (see: https://sciter.com/sciter-and-directx/ https://sciter.com/sciter-and-directx/) , that will definitely beat any possible browser/Electron solution. So script benchmarks are orthogonal to the reality. They make sense in Electron case as JS is the only realistic option to write app code. But not in Sciter case. It is not a browser for that matter.