peerjs VS Pion WebRTC

this app is using peerjs to connect peers over a webrtc connection. check out thier docs for more info. with webrtc, things like file-transfer, should be very performant compared to cloud storage providers... especially over LAN. network speed doesnt seems to be an issue i have experienced.

I'm using the client-side PeerJS https://peerjs.com/ library for networking. As the name may imply, a direct connection is established between two peers using WebRTC via "handshake" through an intermediary server they host - and, they provide source for the server as well. I have found it to be quite reliable, thus far.

You kind of sound like a beginner. The browser APIs are a bit painful to work with. It might be easier to use PeerJS: https://peerjs.com/

If you want you can use Preact. PreactJS is a lightweight alternative to ReactJS, designed for high performance and compatibility. is often used in applications where performance is critical and has a small footprint.

This opens up a lot of neat possibilities, and fortunately I found a very easy JavaScript library for handling multiplayer called PeerJS. The way you can send packets from player to player is very simple and something even a beginner to JavaScript could understand.

You might be able to eliminate the VPS by making it P2P using something like PeerJS [1]. PeerJS provides a free shared connection broker server.

[1]: https://peerjs.com/

Note: peerjs is a good starting point!

We use peer.js module to create a WebRTC connection between clients

Now that we have all the required boilerplate we can start building the actual game. For the communications between peers we are going to use PeerJS a peer-to-peer library built on top of WebRTC.

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.

I have worked four jobs related to https://github.com/pion/webrtc and one for https://webrtcforthecurious.com

Two companies used Pion. The other two were just using the protocol (WebRTC)

In my experience Go has been relatively approachable for people that are good at PHP. It has a great standard library and a pretty solid ecosystem, though frameworks aren’t as popular in Go. There are some well regarded libraries for things like WebRTC via https://github.com/pion/webrtc WebSicket via https://github.com/nhooyr/websocket

Don't try to make RTC yourself, it looks easy, but in fact, it's a really hard problem to solve. Use https://pion.ly/ it's a pretty solid package they also have a discord/slack channel with a lot of helpful people there.

Maybe you can reuse some of this code: https://github.com/pion/webrtc/blob/master/examples/data-channels/main.go