8 ms·
Very nice design and best thing, it's not an Electron app. I will definitely try this reader.
by efiecho 8y ago
Very nice design and best thing, it's not an Electron app. I will definitely try this reader.
- jasano 8y agoJust out of curiosity, may I ask what your bias is against electron?
- mav3rick 8y agoCan't speak for performance but there are definitely security concerns with Electron.
- michaelmrose 8y agoThey perform comparatively slowly and use more resources and battery power. For example hexchat an irc client seems to use about 50-60MB of ram. Slack by contrast out of the box appears to use 1.2GB of memory. There are at present 12 applications open on my machine. If they all used over a GB each something would be starving given that I only have 8. Note please that most machines still have 8GB or less. Do you really not understand why people are biased against electron or are you pretending to for effect?
- jasano 8y agoI just wanted to hear what people had to say to be honest. Given the success of Slack, is it really that bad? Why has no resource "friendly" alternatives taken its place?
- seirl 8y agoBecause people used to be able to use whatever IRC client they wanted for Slack, so it wasn't a problem if they were too memory constrained. In a pure embrace, extend, extinguish fashion, Slack closed the gateway that made them popular and now everyone is stuck with their pile of crap app.
- michaelmrose 8y agoMost users can afford one resource hog even if battery life and performance decrease. We can't afford a whole list of apps all hogging resources simultaneously.
- dotancohen 8y agoNot GP, but many people (myself included) associate electron apps with high memory usage and occasionally high CPU usage.
- bayindirh 8y agoWith 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]
- clownpenis_fart 8y agothere's nothing wrong with electron other than that it is a huge pile of garbage to enable idiot web devs to make desktop apps
- soapdog 8y agoI think your comment even though correct might be less impactful to your computer resources than you wanted. If you're reading books in the epub format, then this app will load a web engine anyway. Epubs are in essence a zipped collection of HTML files, so even though the UI is some snappy non-electron solution, webkit is still loaded and in memory and being used to render the book.
- hombre_fatal 8y agoI saw it depends on libwebkit2gtk, so I assumed it used web technology for its UI.