3 ms·
The project just mentions WebRTC as bloated, it's not WebRTC compatible at all. WebTransport isn't there yet so browsers are hamstrung by not having access to r
by Karrot_Kream 3y ago
The project just mentions WebRTC as bloated, it's not WebRTC compatible at all. WebTransport isn't there yet so browsers are hamstrung by not having access to real sockets.
- ekr____ 3y agoOf course, WebTransport also isn't real sockets. It's more like WebSockets but with more modern transport semantics such as unreliable data and multiplexing without head of line blocking (as long as it's run over QUIC). For security reasons, browsers don't allow Web sites access to raw TCP or UDP sockets.
- Karrot_Kream 3y agoYeah I was being a bit sloppy equivocating the two. WebTransport gives QUIC based messaging in the browser but not TCP/UDP.