It's like shitty iOS cordova packaged web apps - they also require "minimum effort" and "cross-platform functionality". At the tiny expense of horrible user experience.
> What would it take to achieve something like Electron but native? Why hasn't it been done yet?
Are you really that ignorant? Never heard of Qt, SWT, GTK and myriad of other cross-platform tools and widgets used to develop cross-platform apps since the 80s?
VS Code presents a good experience and it's resource usage is more reasonable, it's a good example of a successful Electron application. On the other hand, it has Microsoft behind it and there's probably good reasons why it's so much more performant than Atom, for instance. I am not convinced it's reasonable to expect all Electron applications to hit this relatively high bar in terms of quality.
In my opinion, Electron applications "stick out" as much as any other non-native application, this isn't an advantage to Electron. Indeed, I think Electron has proven that people aren't all that interested in a native application, as long as it's reasonably attractive and the interaction is fun. This could open the door for a new class of cross platform UI toolkit, one that drops the faux-native UI in favor of something simple, attractive and straightforward.
- KDE
- AMD's Radeon control panel
- VLC
- VirtualBox
Qt apps feel far more native than Electron apps in my opinion.
AMD's Radeon: admittedly, I have not used this.
VLC: hardly any UI. Mostly menu items.
VirtualBox: hardly any UI. Mostly menu items.
Edit: formatting.
The Radeon interface does not fit in at all with Windows (nor macOS or any Linux DE I've ever seen, for that matter) and is almost always glitchy for me.
https://appdb.winehq.org/objectManager.php?sClass=version&iI...
Yes, feels strange to think that you need to run a qt app against wine because the publisher does not support gnu/linux.
But it is available on linux via `apt install wine` and downloading the exe.
"Favors developer user experience over end-user experience"
So, something that favors end-user experience over developer experience will produce spanking fantastic apps?
"It's like shitty IOS cordova.."
Like shitty android/ios apps without the cross-platform functionality?
"Are you really ignorant?"
Holy crap! Most of us here know the stuff from the 80's! We also know the awesome stuff we can do with modern tech.
Your comment sucks of classic cargo cow bullshit. Loosen up.
I already know of the toolkits you mentioned, no need to call me ignorant. I have to admit I've never seen a single Qt, SWT, GTK app that looked and felt native. There probably are some but I would argue the effort is much higher than Electron.
I disagree that the comments pointing out the high CPU and memory usage are non-constructive. These are real issues that literally limit the number of Electron apps that can run at a time on a particular machine. Some Electron apps perform reasonably well, VS Code is a good example. But many perform abysmally and Electron is treading dangerous ground by going against the trend of limiting resource usage in order to extend battery life. Indeed, in my experience running a handful of Electron apps is a sure way to shorten battery life.
I think that "Something like Electron but native" is a confusing idea. The browser engine that Electron uses is native to the OS it's running on... As others have pointed out, the best we could hope for is some sharing of the runtime that would allow more applications to run simultaneously.
You mention native languages that have a good cross platform story and I'd like to see some work toward a UI toolkit that is less demanding of resources. While people like Javascript, I do believe some of them will move to another language if they can do what they need to do: deploy to all OS environments with only minimal code changes. If Electron has taught us anything, it's that customer's don't really care that much about an application appearing to be "native".
> I think that "Something like Electron but native" is a confusing idea. The browser engine that Electron uses is native to the OS it's running on...
Here I meant native as in a natively compiled language. The browser is also invisible in this case, and the whole Electron model adds so many layers (which is part of the resource usage problem).
> If Electron has taught us anything, it's that customer's don't really care that much about an application appearing to be "native".
In this case I meant native as in blending in with the desktop environment, which I think Electron apps are more successful at than other toolkits (which are often natively compiled).
In contrast to most other non-constructive comments about how Electron sucks, I think the focis should either be how to improve Electron (as mentioned by others) or on how to improve the cross-platform story for more native technologies.
What makes Electron so attractive is that it is so very close to write once, run everywhere. No other technology today comes close, which I think is evident based on the number of Electron apps out there. There are some native languages which have great cross-platform stories (e.g. Go), but few of them seem have a great fronted story. Today the problem is that all major OS platforms are pushing their own framework and language walled gardens, but I think most developers would like their apps to be cross platform if they could. This is an example of where the community has to do it themselves because the major OS developers seem to have no interest in cross-platform tools.
What would it take to achieve something like Electron but native? Why hasn't it been done yet?