postsack VS imapfw

I've recently used trunk for the first time. It is a huge improvement to the current way of building a Rust wasm app. For one of my apps that doesn't use trunk, I'm maintaining these two scripts to set up a system and to compile a wasm bundle:

- https://github.com/terhechte/postsack/blob/main/postsack-web...

I wrote a cross platform Desktop app that can analyze these email backups to provide a visual clustering of the contents of your mails.

https://github.com/terhechte/postsack

It parses my 13gb Gmail backup in under a minute.

I recently finished a cross platform app written w/ Rust / egui: https://github.com/terhechte/postsack

Coming from Swift, it was actually a fun experience. It doesn’t look very native, but neither does electron..

Another nice Rust ui framework is Druid: https://github.com/linebender/druid

- Image support isn't particularly nice. Loading textures and accessing them at runtime is a bit of a hassle. Here's the code to load a PNG (https://github.com/terhechte/postsack/blob/main/ps-gui/src/textures.rs). In other similar frameworks (say Nannou or Bevy) this is usually one line (https://github.com/nannou-org/nannou/blob/master/examples/draw/draw_texture.rs) (Bevy actually has a very nice handle system to allow access to loaded resources from anywhere).

Backing up my gmail has been on my list for a while (as step 1 of a migration away from gmail). Does anyone haver any experience with this tool, and could compare it to offline-imap (https://github.com/OfflineIMAP/imapfw) or mbsync? For something important like email, I'd probably rather use something only with more battle testing. I guess beyond a backup I would hope to use the offline copy to migrate to a new provider.