3 ms·
Heck yes. I still don't get how so many creators of apps justify choosing Electron to themselves, what with all the downsides (resource usage, power consumption
by eivarv 8y ago
Heck yes.
I still don't get how so many creators of apps justify choosing Electron to themselves, what with all the downsides (resource usage, power consumption, accessibility, security, and so on).
Another GUI-framework I've enjoyed using is wxWidgets, which provides a thin abstraction to a platform's native widgets.
Has a bunch of language bindings, and a pretty liberal license as well.
- h1d 8y agoWhat exactly is the security concern by using Electron? Accessibility is only achieved by the creator's intention.
- eivarv 8y agoWell, it brings the usual web security issues to the desktop, dragging with it much of the browsers' attack surface. Also, there's been a bunch of CVE – there's one [0] in particular that springs to mind. Accessibility is only achieved by the creator's intention. That's a problem. Native widgets come with accessibility built in (to the extent accessibility is supported on the platform in question). [0]: https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/cve-2018-1000136-electron-nodeintegration-bypass/ https://www.trustwave.com/en-us/resources/blogs/spiderlabs-b...
- Gibbon1 8y agoI've used an editor and two IDE's that are built off wxWidgets. They are all fast and responsive. And support Windows, Mac and Linux. As in they 'work' for all three. I think wxWidgets supports a variety of bindings for different languages as well. Never used it but C#/netcore might be a good choice as well. I've only used C# with winforms though, so the danger I'm talking out my ass is high.
- RantyDave 8y agoI did an app on wxWidgets a few years ago. It's really kinda good - a lot like what MFC should've been.