2 ms·
Electron discussions often focus around the battery and memory impact, one other thing I'd mention is the poor access to native features. You get the stuff a we
by wlesieutre 7y ago
Electron discussions often focus around the battery and memory impact, one other thing I'd mention is the poor access to native features. You get the stuff a web browser can do, but for anything else offered by the OS you might need to wait a while.
For example, Apple shipped their first TouchID laptop in 2016, and Electron's support for that landed in v6.0.0 beta 1 just last month.
https://electronjs.org/releases/beta?page=2#6.0.0-beta.1 https://electronjs.org/releases/beta?page=2#6.0.0-beta.1
I'd looked at switching off 1password to BitWarden and that's a pretty major feature to be missing for three years.
Surprisingly, for as much as everyone craps on the touchbar, that got supported by Electron a lot faster than TouchID did. I guess because not all apps need authentication and they can rely on passwords instead, while it's really obvious when an app doesn't have touchbar support.
- jbverschoor 7y agoNot with nativescript.. you just use the brand new api
- mthoms 7y agoDoes nativescript do desktop? Their site seems squarely focused on mobile (iOS/Android).
- kitsunesoba 7y agoThere’s system feature absences that bleed over from Chrome, too. One that comes to mind is the total exclusion of the numerous bits of functionality that macOS provides in text fields, a great example of which is how Chrome has lacked support for macOS text substitution for coming up on a decade now. https://bugs.chromium.org/p/chromium/issues/detail?id=42434 https://bugs.chromium.org/p/chromium/issues/detail?id=42434