libdatachannel VS Pion WebRTC

Also: https://github.com/paullouisageneau/libdatachannel (C/C++)

I'm building a free platform to build such projects. It consists of a web app: roboportal.io and Golang based software which should operate on the robot's side: https://github.com/roboportal/bot_box. WebRTC part is Pion (https://github.com/pion/webrtc). Also, there are a few more bots examples created with this tool: https://github.com/roboportal/bot\_design\_examples

A number of open-source projects also exist, which give developers a great head start if they're looking to build their own infrastructure - the most popular of these include Jitsi, Mediasoup, Janus, and Pion. These projects provide a layer of abstraction and expose a number of helper functions to perform various tasks, such as creating transports, etc. They have helpful guides on how to get started, but you would still face the aforementioned issues regarding scaling, resources, etc.

Hey HN,

For the past couple of years I have been working on open source software[0] + a free book[1] to make WebRTC easier. I am trying to find the other gaps in the space. Would love to hear what people find difficult about it still!

Even if you don't have a solution would be great just to get a feel for where people are at in the space.

[0] https://github.com/pion/webrtc

[1] https://webrtcforthecurious.com

I started (but many many others contributed) to the Go implementation of WebRTC Pion WebRTC https://github.com/pion/webrtc

Along the way I worked on a Go implemenation of DTLS that gets used on its own a bit https://github.com/pion/dtls

In another life I wrote Therac https://github.com/sean-der/therac. A PHP debugger that was viewable from a browser. I was a remote at the time (2015) and it was a great tool to use with others.

I also wrote fail2web https://github.com/sean-der/fail2web a web frontend to fail2ban

I'm currently building a new product with .NET 5 that creates a WebRTC data channel with clients and also sends them video over WebRTC. In preparation, I evaluated the current WebRTC landscape. The gist is that almost all WebRTC implementations are in other languages (usually C++), so native interop is nearly unavoidable if you want to use C#. I ultimately decided to create a small native library (.so file) using the excellent Pion WebRTC library for Go and then created a C# wrapper for it using C#'s native interop APIs (e.g. DllImport, Marshal.GetFunctionPointerForDelegate()). So far this has been working well and I have both data communication and video streams working, but I should add the caveat that I haven't shipped the service to production yet (I'm still a couple months of development away from that).

I meant to mention: I thought about creating an open-source library for the Pion wrapper, but it's currently quite specific to my application in order to reduce the number of calls needed from C# to Go and vice versa. Perhaps I'll write a blog post in the future, though. In the meantime, the approach I took was to start with one of Pion's examples and then turn it into a static library by using cgo to export functions with C linkage and building it as a shared library like this: