rawrtc

Lacks implementation of key features like TURN support, TCP for ICE and STUN, and some transport protocols, as shown in the README's unchecked feature list, limiting NAT traversal options.

Requires proficiency in C programming and manual memory management, making it less accessible for developers accustomed to higher-level languages with garbage collection or built-in WebRTC support.

Depends on meson and ninja for building, with additional steps for enabling certain tools, adding overhead compared to simpler package managers or precompiled libraries.

While efficient for low-resource environments, the single-threaded event loop can become a performance bottleneck for CPU-intensive tasks like real-time media processing or high-concurrency scenarios.