My beef is around your comment where you stated "limited in its resource footprint". Sure, Wails is lighter compared to Electron, but it's still not as lightweight or efficient as a native app. I personally wouldn't pitch it as a "limited resource footprint" app.
> Sure, Wails is lighter compared to Electron, but it's still not as lightweight or efficient as a native app.
Yeah, I think that's fair. I don't think about resource utilization in a vacuum: native apps require I develop three different apps and likely have a lot of CGO dependencies. With Wails and the OS WebView the same client you're used to using on MacOS should work the same or similarly on Linux and Windows within reason. They should also all maintain similar resource utilization profiles. That's why I said it's limited in its footprint, I'm not here to compete with native library performance and native library performance isn't trying to compete with my ability to cross-compile.
I'm currently connected to four networks for 6 days and 18 hours. Compared to other native apps on the same system: so, if I rewrote the application into three separate applications I could probably save ~200 MiB of memory footprint. I'll look into my ability to slim down the memory utilization but some chunk of this is probably the message buffer of each channel.The wails website says "~10MB baseline memory (vs Electron’s 100MB+)" and that sounds pretty reasonable to me. Does it bloat up badly when you start doing things?
For me, opening it. But my PC is old and not beefy enough for heavy things like react.