4 ms·

Sciter does not use website at all, nor any HTML engine provided by the host OS. It is itself an entire HTML,CSS,JS engine.

• deleted 5y ago
  [deleted]
• chrismorgan 5y ago
  Well, roughly-HTML, almost-CSS and fairly-but-not-completely-JS. Historically, TIScript was the biggest problem for web compatibility, being very web-incompatible, but even the QuickJS version is already incompatible with the web in a couple of ways. And its fork of CSS doesn’t implement things like Flex and Grid, but rather something proprietary with similar scope, some advantages, some disadvantages, but mostly just different which I would say is generally a bad thing.
  • synergy20 5y ago
    which is fine. The goal is to make *cross-platform* Desktop GUIs that is also light weight. I think Sciter can define a subset of html|css|js and provide some syntax checker(e.g. this feature is not supported). For Desktop GUIs we don't need all those web APIs etc. Sciter is super light weight comparing to Electron and Tauri.
    • chrismorgan 5y ago
      You very regularly would like cross-platform desktop apps to work on the web as well, or at least to be able to share significant chunks of code. Given that, the fact that Sciter isn’t actually HTML/CSS/JS but rather a superset of a subset of each becomes very notable: you certainly won’t get total code sharing, and you’ll probably even struggle to get significant UI sharing.