DEV Community

Discussion on: In Defense of Electron

Collapse
 
jillesvangurp profile image
Jilles van Gurp • Edited

I have a five year old mac book pro. Quad core & 16 GB. 8 GB is a (bad) choice and has been for some time. Like the author, I have atom open around the clock, slack running. In addition I run stuff like intellij, spotify (which is also a web based UI), chrome, and several docker containers. When my laptop runs hot, the usual suspects are spotify and rogue jvm processes, not atom or slack. Yes atom and slack probably use a bit more CPU and memory than it should but it's fine as long as you have enough RAM.

On the balance of things, optimizing for five year old hardware when writing software for the next five years is not a winning strategy. I can tell you from experience that running a small company targeting more than one UI platform is a royal pain in the ass and a very unrewarding and expensive strategy. It will suck the life out of your company just managing the complexity of that many platforms and getting anything done takes ages. Throw mobile in the mix and you are sure to fail. Most people that actually know what electron is ought to be running decent hardware and are in all likelihood a tiny percentage of your user base. So ignore those people and focus on your real users that actually bring in revenue. As it is, Spotify and Slack are market leading productw, Atom is shaping up to be pretty popular, and I know absolutely nobody in my wide network of developer friends who has done any native desktop UI work in recent years. It's all web based these days. Native UIs on the desktop are dying out rapidly.

The reason that atom is so popular these days is that it actually is pretty damn good. A lot of that has to do with them using electron and using javascript to implement a lot of the features. When it comes to shipping javascript based desktop apps, there are not a lot of options and electron is one of the better ones. Forget about atom being ever reimplemented in something else.