imap-backup VS minivm

Personally, I use https://github.com/joeyates/imap-backup to archive all my emails and then only keep them on the remote server for as long as I need to (basically until I read them and respond or download an attachment into https://docs.paperless-ngx.com )

I use imap-backup to backup my MailCow email boxes.

You'd need an IMAP backup tool. For example: https://github.com/joeyates/imap-backup . Add it to cron if you want it to backup periodically.

Here's a bad idea that may work. https://github.com/joeyates/imap-backup. I used something like this when we migrated from ridiculous email system to exchange. However the clock is ticking on this option as it doesn't support modern authentication.

Imap-backup: Backup Gmail or other IMAP accounts to disk\ (44 comments)

> I developed a unique way to write interpreters based on threaded code jumps and basic block versioning when I made MiniVM (https://github.com/FastVM/minivm). It was both larger and more dynamic than WebAssembly.

I'd be very interested to read more about this. It looks like you are using "one big function" with computed goto (https://github.com/FastVM/Web49/blob/main/src/interp/interp....). My experience working on this problem led me to the same conclusion as Mike Pall, which is that compilers do not do well with this pattern (particularly when it comes to register allocation): http://lua-users.org/lists/lua-l/2011-02/msg00742.html

I'm curious how you worked around the problem of poor register allocation in the compiler. I've come to the conclusion that tail calls are the best solution to this problem: https://blog.reverberate.org/2021/04/21/musttail-efficient-i...

Maybe take a look at MiniVM[0]? It was on HN a couple months ago[1].

[0]: https://github.com/fastvm/minivm

MiniVM: A zero-dependency cross-language runtime on par with LuaJIT and C\ (19 comments)