amazon-kinesis-video-streams-webrtc-sdk-c VS webrtc-nuts-and-bolts

I am trying to use the Kinesis WebRTC C SDK with ROS, but I am struggling to adapt the CMakeLists.txt to make it work. It's unable to compile and gives me this error:

Yes! I have used it in production with these.

* FaceTime @ Apple https://support.apple.com/en-us/HT212619

* KVS and Chime @ AWS https://github.com/awslabs/amazon-kinesis-video-streams-webr.... Lots of security cameras and robots use it, not public though.

* Lightstream https://golightstream.com . Cloud compositing and other magic.

It is kind of amazing everywhere you will find WebRTC. Stadia, Boston Dynamics, Zoom, Meet, Security Systems, Drones etc... It is probable that you use WebRTC in production everyday :)

I dont know if anyone has tried this, but Im trying to get a rPi working with https://github.com/awslabs/amazon-kinesis-video-streams-webrtc-sdk-c and wowza (a streaming engine that supports webRTC).

AWS webRTC(C/Embedded)

I recommend WebRTC For The Curious too, as another comment. Personally, I didn't use WebRTC in C#, but the WebRTC concepts are nearly the same in every different language/platform. Also, you can check out my project and documentation on internals of WebRTC, written in Go and JavaScript: https://github.com/adalkiran/webrtc-nuts-and-bolts . It's not related directly, but another example of usage at my other project, written in Go, Python, and JavaScript: https://github.com/adalkiran/distributed-inference .

I am heavily biased toward WebRTC. Here is my take on it though!

> It's incredibly complex as a specification

What is complex about it? I can go and read the IETF drafts, webrtcforthecurious.com, https://github.com/adalkiran/webrtc-nuts-and-bolts and multiple implementations.

QUIC/WebTransport seems simple because it doesn't address all the things WebRTC does.

> has limitations and numerous issues that set limits in how scalable it can be

https://phenixrts.com/en-us/ does 500k viewers. I don't think anything about WebRTC makes it unscalable.

-----

IMO the future is WebRTC.

* Diverse users makes the ecosystem rich. WebRTC supports Conferencing, embedded, P2P/NAT Traversal, remote control... Every group of users has the made the ecosystem a little better.

* Client code is minimal. For most users they just need to exchange Session Descriptions and they are done. You then additional APIs if you need to change behaviors.

* Lots of implementations. C, C++, Python, Go, Typescript

Show HN: WebRTC Nuts and Bolts, A holistic way of understanding how WebRTC runs\ (0 comments)

You can find it at: https://github.com/adalkiran/webrtc-nuts-and-bolts