desktop-streaming VS relay

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.

It's probable the core will always remain closed. That's both a business and practical decision. However, much like how Sentry have some of their services open-source, we may follow that route.

There's rust stuff too: https://github.com/getsentry/relay

Sentry uses Rust in their backend, check out relay.

Sentry (sentry.io) | senior software engineer, Rust | Vienna, Austria OR Remote (EU) | https://sentry.io/careers/4635809/

As a Senior Software Engineer on our client infrastructure team, you'll join a cross-functional group of Software Engineers that is responsible for the client-facing operation of Sentry. This includes building and maintaining our event ingestion and processing pipeline, most notably Relay (https://github.com/getsentry/relay). This means you will be involved in the design and evolution of both external and internal services, as well as create new mission-critical software at Sentry.

If you like system programming, know Rust (or another systems programming language) and want to work on mission-critical high-volume services, this is the role for you. And your contributions are open source!

Apply here: https://sentry.io/careers/4635809/

Try https://docs.sentry.io/product/relay/

We have no Nim usage in the company. One of our engineers nominated it as something they find personally interesting, and we wanted to give at least a little bit to every project that our employees nominated.

By contrast, we use Rust quite heavily, including our core ingest component: https://github.com/getsentry/relay.

That's why there's such a discrepancy in this case.