←back to thread

86 points stargrave | 1 comments | | HN request time: 0.001s | source
Show context
speps ◴[] No.40084149[source]
It mentions WebRTC but this project wouldn't work in browsers as it's a Go CLI tool. Is there any alternative to WebRTC nowadays? How far along is WebTransport? Anything else that could rely on older web tech?
replies(1): >>40084400 #
Karrot_Kream ◴[] No.40084400[source]
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.
replies(1): >>40086647 #
ekr____ ◴[] No.40086647[source]
Of 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.

replies(1): >>40089625 #
1. Karrot_Kream ◴[] No.40089625[source]
Yeah I was being a bit sloppy equivocating the two. WebTransport gives QUIC based messaging in the browser but not TCP/UDP.