desktop-streaming VS brainf-rs

I'm using webrtc-rs for my personal project and their RTP stack is chock full of allocations/deallocations. I, on the other hand, prefer to use preallocated buffers so I find myself having to reimplement a lot of RTP functionalities.

Finished the native Android client of my desktop streamer and latency still sucks. I looked over at Moonlight's code and they have lots of vendor-specific hacks for lowering latency. But I can't just copy that because: 1) it's GPL, 2) I'm doing the decoder initialization purely in Rust so I don't have convenient access to the Java methods.

I found it easier to integrate NvEnc to webrtc-rs. libwebrtc is too tightly integrated and would need a massive C++ shim. Would like to see how your implementation would look.

Made a desktop streamer using Window's IDXGIOutputDuplication API and the webrtc crate.

Lately I've been getting increasingly interested in the inner workings of interpreters and compilers. Having very little knowledge in this area I thought I would try my hand at writing a Brainfuck interpreter in Rust: https://github.com/sunero4/brainf-rs Right now it seems to be able to interpret programs without loops, but I suspect I will have to rewrite most of it to support them, as I guess they will require being able to peek at instructions without consuming them.