> [...] you treat a non-flattering language as me being frustrated [...]
You're right; I was being presumptuous about your emotional state. I apologize. -_-
Let me try to clarify: Companies like Slack and Nylas and Spotify understand the performance implications of using Electron and it _is_ a real problem, but the _benefits_ of using something like Electron, at least currently, outweigh the performance troubles.
There's simply a _much_ lower cost to iterate quickly on a web-driven application.
That said, we're all frustrated about the performance implications (users and companies alike), and this this is reflected in the direction the industry is taking.
I predict Electron _will_ become less popular in the next year or two as React Native desktop support becomes proven by one or more major players:
> You're right; I was being presumptuous about your emotional state. I apologize. -_-
Upvoted for you being nice and constructive. =) I could've been less harsh myself. Sorry!
> ...the _benefits_ of using something like Electron, at least currently, outweigh the performance troubles.
I get it, man. I've been there in the past. I understand your position.
> There's simply a _much_ lower cost to iterate quickly on a web-driven application...That said, we're all frustrated about the performance implications ...
Not arguing that, that's an undeniable fact.
> ...as React Native desktop support becomes proven by one or more major players:...
Yes. Nothing would make me happier. I started with Windows' crappy MFC, ATL etc. horrifying libraries and I've been immensely let down by the promise of Java Swing community that never managed to get its act together well enough to give you a quick and easy way to create cross-platform UIs. Desktop UI is like a hobo on a celebrity wedding: everybody knows it's there, everybody feels awkward about it, and nobody wants to improve its situation. And that's going for like 20 years now.
Us the slightly older generation of devs are guilty for the situation as well. We too had to go on about our day jobs and find a quick way around.
I guess I was a bit harsh because I expected the next generation to pick up the ball and dribble it better than us... >_< Which is a very wrong and egotistical expectation, I'll be the first to admit.
Just don't give up! Make sure that you educate management periodically. Talk to them, convince them, give them analogical examples from the physical world so they get the problem on their level. Never give up the good fight; educate, iterate, improve.
I loved your app, by the way. I only uninstalled it because I am moving away from Gmail.
I really hope React Native Desktop works but I am very skeptical since there still isn't the same coalition of large companies with apps in production using it. Right now React Native Mobile is being pushed by FB, Airbnb, Tesla, Bloomberg, Uber, Soundcloud, etc. and there are thousands of apps using it. React Native Desktop has nowhere near that momentum or support. It would probably be more effective for React Native Desktop to jump on the ElectronJS bandwagon and use it to push awareness, integration, and distribution since it's a pretty close use case.
You're right; I was being presumptuous about your emotional state. I apologize. -_-
Let me try to clarify: Companies like Slack and Nylas and Spotify understand the performance implications of using Electron and it _is_ a real problem, but the _benefits_ of using something like Electron, at least currently, outweigh the performance troubles.
There's simply a _much_ lower cost to iterate quickly on a web-driven application.
That said, we're all frustrated about the performance implications (users and companies alike), and this this is reflected in the direction the industry is taking.
I predict Electron _will_ become less popular in the next year or two as React Native desktop support becomes proven by one or more major players:
- Linux: https://github.com/CanonicalLtd/react-native
- OS X: https://github.com/ptmt/react-native-macos
- Windows: https://github.com/Microsoft/react-native-windows