When comparing Sciter vs Java / Swing, the Slant community recommends Java / Swing for most people. In the question“What are the best cross-platform GUI toolkits?” Java / Swing is ranked 16th while Sciter is ranked 19th. The most important reason people chose Java / Swing is:
Swing is part of the Java API.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Multi language
Support for C++, C#, Delphi, D, Go, Rust, Powerbuilder. See Go bindings on GitHub. The binding for C# on GitHub, SciterSharp does not seem to be free: in a commercial product you should acquire a commercial license.
Pro Lightweight
Only a single native DLL.
Pro Part of Java
Swing is part of the Java API.
Pro Very good and powerful API
E.g. separate models.
Pro Powerful controls
E.g. JTable which works fine on every platform with very large row counts, e.g. 100.000+.
Pro Several look and feels available
Pro Easy to use
Drag and drop utility.
Cons
Con Linux version is not very mature
The Linux version is missing HTML/CSS features when compared to the Windows version.
Con Not fully HTML5 compliant
Lacking HTML5 functionality and W3C standards: grabbing a library like JQuery or Bootstrap and use it in Sciter will not work.
Con Not WYSIWYG
Not WYSIWYG like WebForms or WPF.
Con Only for JRE-based languages
Con Bugfixes rely on Oracle
Con No real native look
Though the importance of the native look seems to have dropped the last years by the raise of in-browser-applications.
However, you can achieve native look and feel using UIManager.systemLookAndFeelClassName.
Con Severely deprecated
The system is ancient and Oracle has dropped support for it in favor of JavaFX