a) being able to deploy same codebase on web and desktop
b) reusing the vast selection of libraries for web
c) tapping the large amount of trained developers.
Sciter fails on a) and b), because it doesn't support even such a basic and widely used feature as CSS flex (they have something similar, but incompatible).
Even c) is very debatable.
Binary sizes are currently around ~12mb which isn't as good as Sciter but is quite a bit better than Electron.
Desktop UI and Web UI models are so different that in reality you cannot use the same codebase on 100% in both targets.
Web UI uses traditional Web's "endless tape" model where only width is known. This does not really work on desktop where width and height are finite. See this Sciter based app https://notes.sciter.com/ as an example.
> reusing the vast selection of libraries for web
If you do need this then you can use Sciter's WebView that is a <frame> backed by system browser:
https://sciter.com/wp-content/uploads/2022/04/sciter-webview...
> If you do need this then you can use Sciter's WebView that is a <frame> backed by system browser:
iframes are very constrained in what you can do, if you’re targeting the web from the start you get the full power of using those libraries beyond the bounds of a single frame.
I develop an Electron app and the CSS is 100% same on both web and desktop. It's not a "web page", it's an app, which doesn't use the "endless tape" model.
> If you do need this then you can use Sciter's WebView that is a <frame> backed by system browser:
At that point it seems easier to just use something like Tauri which uses the system browser for all rendering.