Revisiting ElectronJS

A couple of years ago, I had stumbled upon the ElectronJSframework from Github. I played around with the program and spawned an idea or two, yet could not for the life of me shake the idea that the Chromium wrapper on steroids was… unnecessary. I understood the intention of bringing web technologies to the desktop environment, although I always figured that if you can accomplish your goal with web technology, why not keep it on the web? At first glance, ElectronJS seemed like an unnecessary bloat to your system to accomplish writing quick and dirty programs without taking the time to figure out a language more appropriate for the job.

My view on this since then has shifted slightly. There is still a plethora of micro-programs, to-do lists, websites-in-an-app and other applications lacking in the form of imagination. And yet, Gitkraken.

Gitkraken is an ElectronJS program that defines what the power of the V8 engine should be used for. I was impressed with the speed and functionality of Gitkraken, and so I opened up to the idea of using more ElectronJS programs. I found useful programs like Abricotine, a visual markdown editor, and… well that’s just about it. There are a few submissions to the ElectronJS apps  page that seem decent enough, but I can’t find a use for them in my development cycle. The page is cluttered with an overwhelming amount of native web-service clients and list managers. It’s a sea of Hello, World‘s in there. Many of the programs aren’t even cross platform, one of the big selling points of ElectronJS!

In short, I’ll give more ElectronJS programs a chance, and maybe even spend some more time sub-atomic, but as for right now… I’ll stick to the native code environments.

Share on FacebookTweet about this on TwitterShare on Google+Email this to someoneShare on RedditPrint this page
Bookmark the permalink.