Earlier quoted context omitted.
However, 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.
> 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.
But again, I'd just include libwebkit (or similar) with a JS engine into my app and be happy.