I just tried that. It works quite nicely, very cool. And NetSurf is designed to be able to output to a framebuffer (with a rudimentary builtin toolkit), yep. (

I just tried that. It works quite nicely, very cool. And NetSurf is designed to be able to output to a framebuffer (with a rudimentary builtin toolkit), yep. (AFAIK you can get it to build the framebuffer mode on top of straight Xlib, for testing that mode on Linux.) NetSurf doesn't do audio yet (no <video> or <audio> tag support for starters) but yeah, an arcan/durdan-based UI would be pretty cool! :P WebGL wasn't a complete failure, it gave us http://acko.net/ http://acko.net/. WebRTC is fun though - I remember someone mentioning (it might've been on here) how they asked a WebRTC implementer why they specified arbitrary TCP/IP communication channels, and the person responded that you might want to use it to talk to your toaster. That functionality lets us have https://webtorrent.io/ https://webtorrent.io/ though, so... The potential worst of WebUSB: cloud-based hardware capture devices, where all your oscilloscope's processing happens in the cloud, and you'd better pay your subscription on time. The potential best of WebUSB: crowdfunded/distributed USB protocol debugging and live sharing - plug in your device (possibly inline with a software-controllable on/off switch, for cold resets), point a webcam at said device, maybe attach probes to some test points, walk away, and it's been reverse-engineered by tomorrow morning, possibly for a fee, possibly for free. This would cover at least 50% of reverse-engineering. I'm not sure how viable it would be through the browser, though... I say let the slightly clinically insane specifications guys go on reinventing all the wheels. They leave a wake of things that open and shut in their path that are just capable enough to actually be useful. \o/