I'll try to counter your arguments, even though I share your sentiments against Electron: * Huge memory impact for your app The same is true for native macOS

I'll try to counter your arguments, even though I share your sentiments against Electron: * Huge memory impact for your app The same is true for native macOS applications. * Non-native look and feel (no, neither Vue nor anything else give a native app experience) Agreed. * Possible security holes, as Electron is patched behind Chrome, and your app therefore behind Electron Security holes with respect to what kind of threat? That is, for an application that gets installed on a computer and runs with user privileges (), what is the kind of threat that could break Chrome/Electron but not a native macOS application? () If we are talking about sandboxed applications, the thread could alternatively be the application breaking out of its sandbox. A different analysis is obviously needed here. * (...) you value their computer resources very little (...) This seems to contradict the suggestion to write a native c/c++ backend. Such a backend can easily optimize the performance-critical parts. Premature optimisation isn't the same as valueing your user's resources. * Electron is the solution when a developer values themselves over their customers. This is a false dichotomy. A developer who makes his/her life easier has more time to work on things that matter, including optimization.