With WASM we get access to load instructions directly to RAM, but safely. I really wish the Web would allow us to do the same for block devices and sockets.
-
Show this thread
-
Custom wire protocols; custom databases. If the Web is set to become the universal portable VM, then we need to finish what WASM started.
1 reply 1 retweet 4 likesShow this thread -
Replying to @yoshuawuyts
Can you expand on these ideas pls? I’m not sure I fully understand
1 reply 0 retweets 1 like -
Replying to @shizzmd
So right now all we have is stuff like Fetch & IndexedDB. These are high level abstractions. I think we need low level abstractions: e.g. WebUDP, WebBlockDevice.
1 reply 0 retweets 1 like -
Replying to @yoshuawuyts @shizzmd
High level APIs have the downside that they don't map well to the OS, giving up performance. To then implement something like a DB on top of it means you'll only get a fraction of the perf you would writing non-browser code.
1 reply 0 retweets 1 like -
Replying to @yoshuawuyts @shizzmd
A whole range of apps (e.g. real-time video games) simply aren't possible right now. It'd be cool if the platform had the capabilities to achieve it
1 reply 0 retweets 1 like -
Replying to @yoshuawuyts
Would that even be possible without violating all the laws of sandboxing? Who would one ask about this? Would
@jaffathecake be a good person to start with?1 reply 0 retweets 0 likes -
Replying to @shizzmd @jaffathecake
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.
2 replies 0 retweets 1 like -
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 
-
-
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 - 3 more replies
New conversation -
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.