Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
Cross platform design philosophy
1P_Ben @MrRooni roustem
I understand a part for you deciding to go for Electron on the front end was so that the Apps could all look and feel as close as possible to each other across the various...
One could open up the arc a little further: As some people have probably noticed, we are slowly burning our asses off. One of the ways out of the dilemma is NOT to waste more energy. I've been wondering for a while now what all these Electron-like apps and other JS hell apps consume more energy than their efficiently programmed counterparts.
Billions of computers and servers operating as if resources were free. I studied technical computer science. I used to develop software for devices with little memory and CPU. I dare say that all those who bluntly pull thousands of node/whatever dependencies into their code can't really develop SW. They can nail together prefabricated boards, but that's about it.
I had compared a few Electron apps to their native counterparts a while back. The bottom line was that the resource consumption was at least 3 to 5 times and even up to 10 times higher. Be it CPU, processes/threads (this also costs resources), RAM and battery. Not only do the apps themselves consume more battery, you also need more and more RAM - and RAM, oh wonder, needs more energy.
There are some projects out there that are also multiplatform. They use e.g. Java or C/C++ as a core and marry this with a corresponding GUI on the respective platforms. Like Cyberduck, Transmission or Handbrake, for example.
