Description
A common thread for people doing game-y/xr-y Javascript is that WebRTC has problems. Smarter people than I have done writeups.
(it is also a slight technical problem for us, but that's beside the point)
Problem
While the "Web" at large is beholden to what consortiums hand down at the pace of RFC, Exokit by design is not.
There is demand for better realtime APIs, and they have already been hacked in to the codebase for that reason. It's easy to window.udp = require('net'), even if it's not right.
But if this is something we want to public sites use we would need a standard for it -- if only because if everyone hacks it in it otherwise has a high chance of being broken by a version update.
Solutions
- Wait for a standards body to solve it in all browsers, then implement
- Push at the standards body for the above
- Make up a standard and try it
- Have a "meta-standard"/flexible plugin interface, where the site can request extra functionality from the browser, like a whitelisted module
- Let everyone hax their own hax and support those efforts
- Take a hard stance and say we won't do anything Chrome doesn't
I haven't thought about this enough to have a strong opinion; just coalescing the discussion.