- better api surfaces: e.g.
- web gpu (or wgpu written in rust) for browser games of gpgpu, or
- web usb, allowing for browser based access to e.g. a software defined radio receiver, so you could e.g. send someone a url, make a p2p session, and do remote radio rx/tx for anything you like
- more consistency across browser vendors, for good or bad (see manifest v3)- more demand-time invoked, one-off compute instances per user, and for cheap or free - see gitpod, vscodeweb
- more synchronization protocols for connecting remote computers together:
- - it would be so easy for somebody to come up with e.g. a BOINC/SETI/F@H-like volunteer compute library all in the browser by using Jax (XLA + free parallelism) -> compiled to webasm + some kinda (isomorphic to a) monoid homomorphism/distributed computation/work queue scheme to just point a bunch of people's computers to a page to do collaborative compute by just sharing a URL