Electron version: 5 processes, total of 132,340 K memory used.
Epiphany version: 1 process, 29,740 memory used.
Trying to stop my battery going flat so fast so I think I'll start trying out more epiphany based web apps.
@ohyran lol 😆
@kezzbracey for battery you also want as few wake-ups as possible. If you haven't already, check out "powertop".
@dnkl Awesome, thank you. That was my next task, learning how to configure a system for minimal battery drain. I have TLP going already but I knew there must be other options too. I'm looking at powertop output now, will go read up on how to optimize.
Also it has had a large number of serious (read: security related) bugs.
And it has caused my desktop to stop booting at least twice, with pretty much no other workaround than to wait for a new release.
@kezzbracey we don't do that much in the native process actually except:
so it shouldn't make a big difference.
We keep websocket open too if there's a logged in window in the background.
I use web app myself, at least for now.
There are couple of things we can optimize for battery life I guess but it was mostly for mobile so far.
@charlag I was pretty much just guessing fewer processes might help on battery, but I've since been told it might not really help.
I'm also trying to move away from Electron in general, and have too many pinned tabs in FF, so it's nice to have another option via Epiphany.
A native app would of course be perfect if that ever came along.
@kezzbracey I think chances are higher that either:
1. We stabilize and document API so that someone else does it or
2. We write IMAP bridge
Neither of which is official position, just me speculating.
Even Electron clients have big maintenance cost because you need to teat a lot of things on a lot of systems, people have no idea how taxing it is for the small team.
@charlag Either of those things would be great. I understand of course that we're all working pragmatically, choosing from among the options realistically available.
I'm also hoping an option 3 emerges: that a project comparable to electron matures as a real alternative for deploying web apps to desktop.
@kezzbracey if it doesn't run on web, it already loses to Electron. We are not in position to give up web.
I see that you're front end dev. You could try poking into the API looking at the client code.
It lets you create a desktop app out of the Tutanota web client using either Firefox, Chrome, Chromium or Vivaldi. I just set it up using Firefox, and so far it's perfect. Frees up some room in my pinned tab section, uses my browser of choice, spot on.
@kezzbracey people recommending bsd and getting rid of systemd for battery life, lmao.
First one doesn't have drivers, second one will throw away battery optimizations away.
I just recommend this from one of the Arch developers:
@charlag Thanks for that! Trying to get myself informed on all the pros and cons.
Linux Geeks doing what Linux Geeks do..