There's nothing wrong with lowering the barrier, but there's quite much wrong with using an overkill for simple tasks. Using Electron for many tasks is like using the engine of a truck to make scrambled eggs.

Is it possible? Of course. Is it a waste of resources? Entirely. So does it make sense? No.

Well, here's the bug report to it, since Microsofts Visual Studio is also programmed with Electron, one user of this found it: https://github.com/Microsoft/v...

This also showed up as an article in The Register: https://www.theregister.co.uk/...

Let's face the truth: Electron delivers a Chromium engine, Node.JS and V8, all rolled into one package to you. So of course it's a memory hog, depending on what you are going to program, like a terminal, clipboard manager or tiny frontend to FFMPEG [all existant projects]. All those programs alone need 200 MB for the runtime engine, to just do really simple stuff.

It also needed 13% of CPU time to just draw a blinking cursor (!).

It's mostly used by shitty webhipster design startups, which are just way too lazy to learn a proper programming language, and it even doesn't fit well with the UI of your operating system. And since the underlying parts of it, when a program gets delivered, aren't for sure update as frequently as Chromium alone, it's a security nightmare as well.