Because one is annual, and the other is just total. The equivalent of GDP for corporations would be annual revenue.

JS has proper async stacktraces as well, or do you mean something else?

You're right. But it was not the case years ago when my team evaluated Go and Node.js. I should have clarified.

Great work!

Strangely, I thought I remember being able to use breakpoints on https://cloudflareworkers.com/ - I thought it handled inspector messages in a nested loop until receiving debugger resume command - since the beginning but I guess I must be mistaken... Maybe that was just an idea we had back then.

Thats still work, breakpoints using devtools works like any other source. Its not the same but helps.

Hm what's the difference then?

> What prevents developing a wrapper or shim that runs any wasm as if it were any other native executable?

That definitely exists and is used on server-side - Wasmtime, Wasmer and others.

Don't know about webcams - usually (unlike in OP's case) those already have good OS-level support, but I did port gphoto2 to Wasm+WebUSB for access to DSLRs & mirrorless cameras: https://github.com/GoogleChromeLabs/web-gphoto2

Amazing, thanks for sharing

And really great write up too!

https://web.dev/porting-libusb-to-webusb/

Thanks, be sure to check out the part 2 as well :)

Browser ports can't integrate at OS level, they're intentionally separated today, but given that e.g. Node.js has WebUSB support (https://github.com/node-usb/node-usb), I guess you could make a layer that exposes such Wasm drivers as native to the OS. Could be a fun experiment.

Chromebook is probably the perfect target for those kinds of ports. Definitely worth giving a try, hopefully SANE supports it.

Thank you!

That's been already blocked by Google, with reviews deleted, so not much I guess.

> Not to mention that I have almost no clue how to debug a WASM build.

I've got you covered: https://developer.chrome.com/blog/wasm-debugging-2020/ (TL;DR use Chrome DevTools with the official DWARF integration)