4 ms·

I invite you to try Sciter[0], it allows you to write your frontend in HTML, CSS and JS, but the backend of the app can be anything native you want (C++, C#, Py

I invite you to try Sciter[0], it allows you to write your frontend in HTML, CSS and JS, but the backend of the app can be anything native you want (C++, C#, Python perhaps). The events in the HTML DOM interface with methods in the native code, so your button actually runs the fastest, because the business logic of the app is native. Some of the most performant products use it, like antivirus products. Yet, you see antivirus products have a nice GUI and that's the reason. You can see it in the showcase. I know Sciter is not mainstream, but you don't have to deal with Qt's API nor with making your business logic in Javascript with Electron and shipping the greatest overhead that an embedded browser implies. To me, it's the best of both worlds. Flexible do-as-you-see-fit GUI and native performance because of compiled languages. [0]: https://sciter.com https://sciter.com

IshKebab 5y ago
You can write your backend logic in whatever language you wish with Qt or Electron too. You also neglected to mention that Sciter is closed source which is a pretty big turn off. > antivirus products have a nice GUI They do?? > deal with Qt's API. Qt's API is one of the best designed that I've ever used.
- ivanmontillam 5y ago
  > You can write your backend logic in whatever language you wish with Qt or Electron too. Yeah, but most developers won't in the case of Electron. It's a source of CPU Perfomance abuse. Developers will take the shortest/easiest route, businesses will save costs on development at the expense end-user software performance. See [1]. It's almost always best if your framework protects you from shooting yourself in the foot. That's why some languages support Static Typing, Type Inference, Clear Inheritance rules, among other failsafes. In this case, Sciter protects you from bloat-by-default GUI code. > You also neglected to mention that Sciter is closed source which is a pretty big turn off. That's not true. The source code is available for review if you pay for the license. It's not a turn off for businesses that do need continued support and a contract to back it up. There was an effort to open source it, but it didn't took off in the past year. See [2]. > Qt's API is one of the best designed that I've ever used. Yes, it's nice and all. I've used it myself in about 5 projects. I didn't try to imply it's hard to use or somewhat cumbersome. However, sometimes I prefer not to have to deal with Qt's Theming or I really need custom controls I'd rather develop with web technologies rather than with Qt, at the same time not bundling an entire Chromium + Node 300mb+ package. Sciter does the job for less than 2 Mb, and to me that's unparalleled advantage over Electron. [1]: https://www.ivanmontilla.com/blog/economics-of-software-performance https://www.ivanmontilla.com/blog/economics-of-software-perf... [2]: https://www.kickstarter.com/projects/c-smile/open-source-sciter-engine https://www.kickstarter.com/projects/c-smile/open-source-sci... EDIT: Typos and clarity.

IshKebab 5y ago

You can write your backend logic in whatever language you wish with Qt or Electron too. You also neglected to mention that Sciter is closed source which is a pretty big turn off. > antivirus products have a nice GUI They do?? > deal with Qt's API. Qt's API is one of the best designed that I've ever used.

ivanmontillam 5y ago
> You can write your backend logic in whatever language you wish with Qt or Electron too. Yeah, but most developers won't in the case of Electron. It's a source of CPU Perfomance abuse. Developers will take the shortest/easiest route, businesses will save costs on development at the expense end-user software performance. See [1]. It's almost always best if your framework protects you from shooting yourself in the foot. That's why some languages support Static Typing, Type Inference, Clear Inheritance rules, among other failsafes. In this case, Sciter protects you from bloat-by-default GUI code. > You also neglected to mention that Sciter is closed source which is a pretty big turn off. That's not true. The source code is available for review if you pay for the license. It's not a turn off for businesses that do need continued support and a contract to back it up. There was an effort to open source it, but it didn't took off in the past year. See [2]. > Qt's API is one of the best designed that I've ever used. Yes, it's nice and all. I've used it myself in about 5 projects. I didn't try to imply it's hard to use or somewhat cumbersome. However, sometimes I prefer not to have to deal with Qt's Theming or I really need custom controls I'd rather develop with web technologies rather than with Qt, at the same time not bundling an entire Chromium + Node 300mb+ package. Sciter does the job for less than 2 Mb, and to me that's unparalleled advantage over Electron. [1]: https://www.ivanmontilla.com/blog/economics-of-software-performance https://www.ivanmontilla.com/blog/economics-of-software-perf... [2]: https://www.kickstarter.com/projects/c-smile/open-source-sciter-engine https://www.kickstarter.com/projects/c-smile/open-source-sci... EDIT: Typos and clarity.