ps_mem VS awesome-tauri

I use a script I call memtop10.sh that uses a combination of ps and ps_mem.py which you can find here: https://github.com/pixelb/ps_mem/blob/master/ps_mem.py

Do you mean something like this: https://github.com/pixelb/ps_mem

ps_mem https://github.com/pixelb/ps_mem

Just as a reference, the application I'm building features a lot things inside the final binary, that might affect ram usage, so this is not a "hello-world" example but a real application, with a SPA built-into the binary and loaded into RAM, together with a HTTP API and more (fuller list here: https://news.ycombinator.com/item?id=31765186).

With that said, `ps_mem` (https://github.com/pixelb/ps_mem) reports that the memory usage is 58.7 MiB after starting the Tauri application. If I run just the HTTP API, memory usage ends up being 19.4 MiB. So I guess in that sense, the overhead of Tauri is about ~39.3 MiB.

I'm not sure if it's still working since I've not used it for a while but you can get accurate reports with ps_mem

I find it fresh and positive that Tauri developers take security very seriously. Before this 1.0 release they ordered a full security audit for the codebase and published the report ( https://github.com/tauri-apps/tauri/blob/next/audits/Radical... ).

The project encouraged me to better my own workflows too, as even the awesome-tauri repo requires signed commits in the PR template :) ( https://github.com/tauri-apps/awesome-tauri/blob/dev/.github... )

Tauri if you are already with Rust.

Here are some open source app built with Tauri

https://github.com/tauri-apps/awesome-tauri

I don't at all expect users to do full code inspections, expecting that would frankly be naive in my opinion for small projects like these. I was just trying to alleviate, not resolve, security concerns. What I am trying to encourage is peer review rather than user review of the code. That's a big reason why I have submitted it to developer resource lists such as Awesome Tauri, to get public peer review.