Looks cool. Does it have the capability to do SFU or is there planned work to include that capability ?
They have this SFU example but I didn't look at it closely yet: https://github.com/pion/example-webrtc-applications/tree/mas...
Modern and Cross Platform Stack for WebRTC
31–40 of 49 posts
Re: Modern and Cross Platform Stack for WebRTC
#32> Ship to Mobile, Desktop, Servers and WASM all with one code base. Dumb question: what would a WASM implementation be useful for? Browsers don't expose "raw" TCP or UDP connections, so even if you have a fully working WebRTC implementation in WASM, there would be no way to connect to anything when ran inside a browser. Or is this for WASM use outside the browser?
People are building server-side WASM runtimes, which I suspect is your answer. To me the other answer is they could provide the same API in the browser through a shim.
It's the latter. See https://github.com/pion/webrtc/pull/479
Re: Modern and Cross Platform Stack for WebRTC
#33Interesting! Personally I am looking forward to a Rust implementation.
Yeah me too, what's the deal in Cargo with developers sitting on package names with empty code repos.
This guy has a bunch of webRTC related ones: https://crates.io/crates/webrtc
Re: Modern and Cross Platform Stack for WebRTC
#34Has anyone noticed "Modern and Cross Platform" usually means Golang?
This industry is insanely fad driven. Every aspect of it. Terminology, tech stacks and methodologies are all one fad after another.
Lots of products, including ours, running on Go. It's not a fad, it's a useful tool. Not the best programming language in the world, but still allows you to produce great results in a short time. Kind of like Delphi what used to be for the Windows desktop.
Re: Modern and Cross Platform Stack for WebRTC
#35Has anyone noticed "Modern and Cross Platform" usually means Golang?
This industry is insanely fad driven. Every aspect of it. Terminology, tech stacks and methodologies are all one fad after another.
I’m not sure Go is what I’d call a fad.
Is Java a fad? Its early years were much more hype driven than Go has been at any time during the 10 years Go has been around.
Python? JavaScript? Ruby? Rust?
What I like about the Go community is that it appears to be very measured. Unlike many other communities where the way a language is used becomes bigger than the language. Like Spring and Java. Rails and Ruby.
Or Rust and “look I reimplement X despite nobody giving two shits”. :-)
(My big disappointment with Rust is that it hasn’t found its niche. I’d like that niche to be embedded operating systems. We could certainly use Rust there, because C, C++ and the utterly shit Python-junk used to stich things together is just painful . Competing for attention in server development or any other area that has very strong contenders is clearly an uphill battle)
Re: Modern and Cross Platform Stack for WebRTC
#36> Ship to Mobile, Desktop, Servers and WASM all with one code base. Dumb question: what would a WASM implementation be useful for? Browsers don't expose "raw" TCP or UDP connections, so even if you have a fully working WebRTC implementation in WASM, there would be no way to connect to anything when ran inside a browser. Or is this for WASM use outside the browser?
People are building server-side WASM runtimes, which I suspect is your answer. To me the other answer is they could provide the same API in the browser through a shim.
> they could provide the same API in the browser through a shim.
Oh, so in the browser, it would just fall back to the native WebRTC implementation? That would make sense.
Re: Modern and Cross Platform Stack for WebRTC
#37Earlier quoted context omitted.
For anyone curious, there is a great article [1]. WebRTC enables peer to peer communication. BUT... WebRTC still needs servers: For clients to exchange metadata to coordinate communication: this is called signaling. To cope with network address translators (NATs) and firewalls. ------------- [1] https://www.html5rocks.com/en/tutorials/webrtc/infrastructur...
You need a signaling channel to your peer. This doesn't have to be a server, but it makes things simpler.
My preference is IPoAC.
Re: Modern and Cross Platform Stack for WebRTC
#38How's the native Android / iOS integration story for Pion? Are there any Java / Kotlin / Swift bindings around?
I have the same question. If it doesn't work on iOS it's not a cross platform stack. iOS is the third most popular operating system in the world after Android and Windows.
Re: Modern and Cross Platform Stack for WebRTC
#39Whenever these threads pop up I always ask: is there an erlang/elixir implementation anyone knows about? I check every couple of months and come up empty (there is one closed source one.) Being able to speak WebRTC natively to a Elixir/Phoenix cluster would be a pretty killer app, but the hurdle to get there is quite high.
Re: Modern and Cross Platform Stack for WebRTC
#40What are the best resources to learning WebRTC at the minute?
It seems to be a pretty fast moving area, a lot of what I find out there is outdated.