When comparing Tk vs Sciter, the Slant community recommends Tk for most people. In the question“What are the best cross-platform GUI toolkits?” Tk is ranked 9th while Sciter is ranked 19th. The most important reason people chose Tk is:
Once you understand how to style, the styling can look great.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Easy styling
Once you understand how to style, the styling can look great.
Pro Great for beginners
Easy to pick up and run with it.
Pro Easy and good looking in Mac, Linux and Windows
Pro Bindings for several languages
Bindings for Python, C, C++, Ruby, Perl, Go, Java, Haskell and more, see Languages with a Tk binding.
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.
Cons
Con Base looks are garbage without a good amount of styling
Going with the base look for your app is a bad idea because it looks like garbage with the defaults.
Con C# support lacking
Although the Eagle Project exists, which offers Mono and .NET Core support, C# support is not standard.
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.
