desktop-streaming VS Lariv

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.

Just finished epoch inserts on Lariv, which somehow I managed to implement as a zero-cost abstraction. Currently I'm trying to fix the use-after-free vulnerability I found on the O(1) accesses implementation without sacrificing any performance.

Optimizing lariv, but I don't think there's much to do left. I have some ideas I'll try out, but that's it.

Implementing O(1) get() & remove() speeds on Lariv, a thread-safe vector with lots of quirks.

I just finished my abomination, a linked atomic random insert vector. https://github.com/Alonely0/Lariv