webrtc VS tauri

webrtc

webrtc.rs is a port of Pion (which we also use). It's a better fit for server-side use

I want to use peer-to-peer communication and data transfer for my next side project (client-server web app). I've been doing some research and WebRTC seems to be the only option for this on the client. There are a ton of libraries and product offering for facilitating STUN/TURN servers as a service, but I'm quite interested in learning more about these protocols. That being said, I'm not the best rust programmer (part of the reason of using Rust as the server is so that I can learn more), and the signalling protocols seem rather complicated. I've looked at https://github.com/webrtc-rs/webrtc and it seems promising.

Regarding webrtc-rs. I'm a contributor to that project. The future of str0m could very well be to roll it in under that umbrella. However in these early days, I think it's better to keep str0m separate, until such time that it covers most of webrtc-rs functionality. Discussion here: https://github.com/webrtc-rs/webrtc/issues/230

This project was really fun for me is that I got to use https://webrtc.rs webrtc.rs Rust implementation of WebRTC that is based on Pion. The performance is fantastic and it is so easy to fetch + build. I had a great experience with it. It is really impressive how far the project has come!

I'm confused, you're saying as far as you can tell webrtc-rs does everything pion can do, but also saying "when the project is ready"? Can you explain what you mean? Also it seems webrtc.rs website says it's not production ready yet? How true is that?

The "Mediasoup" project provides a high level JavaScript/TypeScript interface to the WebRTC APIs. The core logic of this project is implemented in C++/Rust. Consider taking a look at the project if you want an easy-to-use library instead of the low-level libWebRTC APIs. A notable project to mention is the Pion/webrtc project which has a Golang implementation of the WebRTC API. Of course, we should mention the rust port WebRTC.rs. Let’s keep all the rustaceans happy too!

Have you considered using webrtc? It's a well-established protocol supported by all major browsers, and there's already a pure-Rust implementation you might be able to use.

If you ever did decide to add the complexity of RTC, my personal favorite SFU is MediaSoup with Janus a second. But if you want to be adventurous the Rust WebRTC project would be your go to. In any case cool project!!

Yup, WebRTC can do this. In Rust there's webrtc.rs which I've been contributing a fair amount to. Check out this example the SDP that's provided via $BROWSER_SDP and the subsequent answer that is pasted back into jsfiddle is the two way connection that /u/anlumo mentioned. With a server this is typically done with a POST request.

Does it have an industry presence? I couldn't find any testimonials on their site. For example https://tauri.app/ is a UI framework in Rust and it is sponsored by some major companies

Interesting, I was just about to try using Tauri with Scala and Scala.js.

Native GUI programming in Rust seems immature from last I checked, but maybe the situation is better than I remember. There’s Tauri. Unfortunately it’s still kinda web-based like Electron, but an improvement still. It uses native webviews and almost everything will be running in Rust, so it may be decently efficient.

Tauri + Svelte is also an alternative

Yeah, I’m using https://tauri.app/

The DX is a thousand times better than Electron. The ecosystem is not as rich yet, but it’s getting there. The Discord community is very active and passionate about the project as well.

I’m also having a great time learning Rust!

They already are – there's a system webview on Windows and macOS. There are a few "Electron alternatives" that use the system webview instead of bundling a copy of Chromium. Tauri [0] is one of them, built around Rust, and it's pretty great. I built a video editor with it.

The usual complaint against this is that you have to support multiple browsers (Edge/Chromium on Windows, Safari on Mac).

0: https://tauri.app

Tauri was the obvious choice for the cross platform application. With 57.3K stars on Github and growing, it is a framework loved by the community. It combines your favourite frontend frameworks with a Rust backend to build "smaller, faster, and more secure desktop applications".

Why wouldn't you just use Tauri for that?

No, I'm using Tauri https://tauri.app/ so that's Rust on the backend doing the interface between the UI and Kubernetes. Solid.js on the UI because it's much lighter/faster than React.

An opinionated way to develop tauri desktop applications powered by html and css where you do not write any client code (no javascript, no webassembly) as all html rendering and event handling is done inside your tauri application. pâro has the minimal client code that is still required already done for you. No more https calls or dealing with JSON serialization.