Earlier quoted context omitted.
150MB might not seem like much, but it really is a lot. iStat Menus, which is tracking a lot more data across my system to render its multiple graphs is using ~85MB total. Bearing in mind that many users are going to have 5 things like this in their menubar, they can't all use this amount.
That's a good point. There's definitely ways to optimize for less memory usage. We've been prioritizing feature development, but plan to focus on this before we start scaling.
~150MB is a huge memory footprint for something that just sits in my menubar idle. Not all Macs have >16GBs of RAM (and even if they did, this is pretty wasteful). I'm also concerned about the battery life.
I'm pretty sure you'll eventually reach a point where it's no longer possible to optimize it any more (nonetheless Electron is just a Chrome instance). If you suddenly realize the whole thing would be twice as good if you'd just make a native app instead, it's better to have no features than have to rewrite all of them.
I know this doesn't sound constructive, but why go with Electron in first place? It's a menubar widget which the users are expected to be running all the time. There's a difference between running a simple applet and a whole browser instance.
