No, this isn't a reason. They're Mac-only because they used Cocoa, which is exclusive to macOS. If they'd used GTK or Qt they could have shared 90% of their application code between at least the three major desktop operating systems, without using Electron.
(At Remotion) We decided against Qt partially based on my experience working on the Dropbox desktop client—Qt sounds great in principle but in practice we think you're better choosing between native or web tech.
I'm less familiar with GTK.
Qt is a particularly poor experience on macOS. Also the past few years all the new stuff in Qt was QtQuick, which seems basically like JS, and if you're into JS, why not just use Electron?
GTK is a non-starter for something professional, at least if the experiences of the GIMP and Inkscape on macOS are representative. (Also, it's C, which does avoid some ABI problems, but it's hardly suited for an object-oriented environment)
Yes, and? "How much code we get to share between platforms" is an extremely poor indicator of quality for any technology. GTK/Qt have the advantage of being very fast, having native look-and-feel, and allowing you to share code between platforms. Electron only has that last one.
If you want to maximize code-sharing, you would use webtech for all platforms, including iOS and Android. Yet most organizations don't, because they know that that gives them a poor experience, and they're willing to expend the effort to do native ports to those platforms.
Alternatively, if I'm not making a web application, I literally don't care about the fact that I could share my desktop code with it, because it doesn't exist.
> My point is that those who can’t use your app would appreciate electron
...and my point is that nothing about Electron makes it uniquely able to solve this problem. Someone who can't use my app would also appreciate GTK/Qt if it allowed them to use it.
Some people are also unable to use apps because they use Electron. My computer can't play some video games while I'm in a Discord call because of how many resources it uses, but it's perfectly fine in a Mumble call, because Mumble has a reasonably-performant, non-Electron client.
