webrtc VS aiortc

I thought i'd share a library that's inspiring some mad science for me based off the amazing work of https://webrtc.rs/. I wanted to make it as dead simple as possible to setup a data channel with a web page.

https://github.com/webrtc-rs/webrtc Webrtc looks feature complete now, may be a good start for web streaming part. https://github.com/cssivision/ytdl youtube download implementation.

WebRTC.rs just released v0.1.0 (https://github.com/webrtc-rs/webrtc/releases/tag/v0.1.0) with plenty of Examples (https://github.com/webrtc-rs/webrtc/tree/master/examples#rea...) to show how to build media and data channel applications with webrtc-rs.

WebRTC.rs is a pure Rust implementation of WebRTC stack, which rewrite Pion WebRTC stack in Rust.

Actually, more Media/DataChannel examples have been provided in https://github.com/webrtc-rs/webrtc/tree/master/examples

Take a look at webrtc.rs, they have already implemented a pretty good subset of WebRTC

webrtc-rs(Rust)

One of the webrtc.rs contributor is also a pion.ly contributor, and the other two describe themselves as gophers/rustaceans. So I'm sure that this rewrite has better motivations than "Go bad, Rust good".

https://github.com/webrtc-rs/webrtc (Rust)

You can't use Django for that, RTC is a separate protocol from HTTP. Check out https://github.com/aiortc/aiortc for a Python-based RTC stack. You write code in there which does the data processing and calls HTTP APIs or something on the Django side.

I am using this python library: aiortc/aiortc while primarily using this example.

aiortc(python)

I am sure there are even more implementations that I am not aware of.

* https://github.com/pion/sctp

* https://github.com/aiortc/aiortc/blob/main/src/aiortc/rtcsct...

* https://source.chromium.org/chromium/chromium/src/+/main:thi...

* https://github.com/sctplab/usrsctp

People don't make these decisions for technical reasons only. Career wise it is a bad choice to spend your time working on pre-existing technologies. You don't become a distinguished engineer by iterating on existing technologies. You become one by being the creator of something new.

I think QUIC is great and does a good job solving the problems it was designed to solve. It is disingenuous to pretend these decisions were made only for technical reasons.

According to aiortc developper, there is currently a bug in Firefox: https://github.com/aiortc/aiortc/issues/481

Fortunately, we can use aiortc, a great open-source WebRTC library for Python. We will start by running the sample code and then learn about WebRTC based on it.

I am using aiortc. In fact, I have been experimenting with a modified version of that example: https://github.com/aiortc/aiortc/tree/main/examples/server

https://github.com/aiortc/aiortc (Python)