4 ms·
With electron, you're running a full chromium at the back end for any task. This increases memory and CPU consumption a lot. Atom consumes as much as RAM as Ecl
by bayindirh 8y ago
With electron, you're running a full chromium at the back end for any task. This increases memory and CPU consumption a lot. Atom consumes as much as RAM as Eclipse for example. Also it's slow due to this load it creates.
For simple tasks, a full fledged, programming capable text editor can fit into ~60MBs. Atom needs 660 just at the start. With that amount of RAM usage, I even cannot open large files as reliably as vim for example.
- criddell 8y agoBut an ebook reader is basically a web browser. This seems like a place where an Electron app might make sense.
- bayindirh 8y agoHowever, it's all static HTML. An HTML rendering library will use less CPU and RAM than a full fledged web browser, and will be much easier to maintain. Calibre's e-book reader uses ~100MBs when opened. It runs independent of the main Calibre app, in its own process. Again, an Electron app will be heavier here.
- criddell 8y ago> However, it's all static HTML No it isn't. For example EPUB 3 supports all kinds of dynamic content including music and video and javascript.
- bayindirh 8y agoHonestly, I wasn't aware. I'm just an old-school guy who uses EPUB to read novels and tech books :) But again, I'd just include libwebkit (or similar) with a JS engine into my app and be happy.
- deleted 8y ago[deleted]