"Microservice" architecture is good alternative

I have some projects with a WebRTC video call component. The way I've found to work with that is to use C++ for a "helper" video call process which uses Google's WebRTC library, and then the rest of the system (be it written in Rust, or Go, or maybe even that too is C++) communicates with the WebRTC helper process via IPC (typically line delimited JSON via stdin/stdout, maybe shared memory or DMA buffers for decoded video frames).

But because WebRTC is complicated, this C++ helper process still ends up being quite large. It would've been nice if that code too could've been written in something nicer. Carbon is interesting for that.

And then of course we all call into C libraries all the time, either directly or indirectly through a wrapper.