TelloGo VS werift-webrtc

AV1 support is already available in libwebrtc!

So when I started building Pion the target use case was to make it easier to build scalable servers. Instead of interacting with a WebRTC servers REST API to query information/load balance I wanted to have it all in one code base. It also is really useful to have Media+Transport decoupled. Lots of use cases I didn't realize grew out of that.

* Teleoperation/robotics (https://github.com/Ragnar-H/TelloGo)

* Control remote software (https://github.com/m1k1o/neko)

* Cross platform file sharing (https://github.com/saljam/webwormhole)

* Sending pre-recorded media (RTMP/HLS/RTSP -> WebRTC)

* Custom DataChannel servers/bridges (https://snowflake.torproject.org/)

Lots of other cool ones in https://github.com/pion/awesome-pion I need to update it. It has been a bit since I have looked through https://pkg.go.dev/github.com/pion/webrtc/v3?tab=importedby

Control drone over browser

I am really excited about https://github.com/sepfy/libpeer. It has examples ready for ESP32 etc....

When working on KVS I wasn't familiar with the embedded space at all. I saw 'heavyweight' embedded where you were running on Linux. Then you had RTOS/No OS at all. I wasn't prepared for these devices at all. If we can make WebRTC work in the embedded space I think it will really accelerate what developers are able to build!

Remotely driven cars, security cameras, robots in hospitals that bring iPads to infectious patients etc... Creative people are building amazing things. The WebRTC/video space needs to work harder and support them :)

-----

I love how diverse the WebRTC space is now. Outside of this implementation you have plenty of other options!

* https://github.com/shinyoshiaki/werift-webrtc (Typescript)

* https://github.com/pion/webrtc (Golang)

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

* https://github.com/algesten/str0m (Rust)

* hhttps://github.com/sepfy/libpeer (C/Embedded)

* https://webrtc.googlesource.com/src/ (C++)

* https://github.com/sipsorcery-org/sipsorcery (C#)

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

* https://github.com/elixir-webrtc (Elixir)

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

* GStreamer’s webrtcbin (C)

See https://github.com/sipsorcery/webrtc-echoes for examples of some running against each other.

This is not true, there are actually multiple WebRTC implementations in different languages besides the reference library: aiortc (python), libdatachannel (C++), sipsorcery (C#),webrtc-rs (rust), werift (Typescript), and Amazon Kinesis (C)

There's a native implementation that requires no binaries here: https://github.com/shinyoshiaki/werift-webrtc

Maybe I'm missing something but how is this one preferable?

Lots of great WebRTC implementations exist. Do you want to stick with node.js?

I am a big fan of https://github.com/shinyoshiaki/werift-webrtc it is pure Typescript.

Check out https://github.com/sipsorcery/webrtc-echoes for all the other implementations.

werift(TypeScript)

https://github.com/shinyoshiaki/werift-webrtc (Typescript)