If WebAssembly was possible, then I'm sure the same can be done for networking & disk access. Probably the hardest part will be agreeing that it's a challenge that needs a solution.
-
-
Replying to @yoshuawuyts @shizzmd
I don't think it's quite the same. We've been able to write to memory for ages on the web, eg assigning a string to a variable. Not sure how you'd expose UDP without breaking security.
3 replies 0 retweets 3 likes -
If they're still a thing, webrtc data channels were supposed to solve the low-level connection control: https://www.html5rocks.com/en/tutorials/webrtc/datachannels/ … Not quite raw sockets but could handle a lot of cases.
1 reply 1 retweet 4 likes -
Yeah, they're rather limited tho; believe ~7 connections is when computers start melting. Also, afaik there's about 2 working implementations around, and building them is considered a feat. So everyone on the server is mostly just shelling out to Electron
1 reply 0 retweets 2 likes -
Clients melt or servers? New server implementations is probably the quickest way to have something real since it is in the field in Chrome and Firefox already
1 reply 0 retweets 1 like -
Clients melting. Maybe my info is outdated, and WebRTC perf has improved since a year ago!
What do you mean by the latter comment tho? I'm not sure I follow.1 reply 0 retweets 0 likes -
If servers are shelling out to electron and not scaling then we probably need more implementations that can scale (Go comes to mind). If clients are melting then please file bugs.
2 replies 0 retweets 0 likes -
Haha, I believe servers are shelling out because not even full-time compiler engineers can get the chromium implementation to build standalone
My understanding is that the WebRTC protocol is mad complex; all the STUN,TURN stuff is tricky. Hence talk about alternatives.2 replies 0 retweets 0 likes -
+
@juberti who should know for sure but in the browser<->server case it might be nice to be able to skip the P2P discovery and not have to implement it in a server lib.1 reply 0 retweets 1 like -
Replying to @patmeenan @yoshuawuyts and
The server lib can be much thinner; it only needs to do ICE Lite + DTLS + SCTP. You can reuse the code from libwebrtc, or use an existing impl like libjitsi. We are working on simplifying the stack to be just ICE Lite + QUIC, which should increase the # of implementations.
1 reply 0 retweets 5 likes
Replying to @juberti @patmeenan and
QUIC would be super! 
1:11 PM - 29 Nov 2017
from Berlin, Germany
0 replies
0 retweets
1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.