To me it was that all tutorials are very outdated, using deprecated browser APIs, and/or using packages and services that abstract away WebRTC (SimpleWebRTC deprecated package and service, PeerJS, etc...), and none of them using TypeScript.
So I wrote my own WebRTC app that solves all of those issues [0].
I really liked your book, but there's no code in it at all, and I'm a person that learns more by following examples and applying them.
I honestly found it a bit weird that a book about WebRTC has no code at all.
Thanks for your contribution and maintaining the pion library(I am a user). The thing is that WebRTC usually isn't a complete solution, many don't want to have p2p but a p2s2p(which usually means distributed computing/SFU) solution, which makes developing an application way too complex.
Thanks for your work -- I've used pion before myself.
Then you know the answer to that question. I imagine on a thread like this that would only tread the surface of the complexity, the first question will always be "What the hell even is STUN, TURN, ICE, SCTP, DTLS, SRTP?"
And thats the beginning of the complexity. But it's also a naturally complex problem. So, I thought it was a joke.
So I wrote my own WebRTC app that solves all of those issues [0].
I really liked your book, but there's no code in it at all, and I'm a person that learns more by following examples and applying them.
I honestly found it a bit weird that a book about WebRTC has no code at all.
[0]: https://github.com/adhamsalama/webrtc