RReverser

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?

Hm what's the difference then?

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.

> 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.

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

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

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)

Or it could apply gzip/brotli + optionally wasm-opt and cut the size ~5-6x: https://twitter.com/RReverser/status/1494435774003093515

The sad part is, it could be cut very easily cut down to ~60MB with basic optimization & compression (heck, even gzip/brotli compression alone would go a long way): https://twitter.com/RReverser/status/1494435774003093515

Impressive feat, but I'm worried this small detail ruins the first impression for way too many.

Part 2 is out: https://news.ycombinator.com/item?id=30165184

Ah, I see. That would be interesting, but removes the cross-platform compatibility from the equation, which, for me, is the most valuable piece of WebUSB and other similar APIs.

Glad to hear! If you want to give it another try, you should be able to use my linked libusb fork in any app that depends on libusb, and compile that with Emscripten.

I didn't see it but did think about it. I think it should be possible by wrapping WebUSB into something like Comlink, e.g. I know Surma experimented with allowing Comlink to be used with WebSockets: https://twitter.com/dassurma/status/1218207376899235840

Comlink takes care of the RPC part of any API, so you only need to choose and hook up a communication backend.

With guiding you're usually aiming for 5-10 minute exposures per frame. That usually results in each frame having at least several streaks. Sure, those are technically still short and can be cancelled out, but astrophotography is already challenging enough and has plenty of other noise sources without adding more fuel to the problem.

And that's now, when we're not close to the planned tens of thousands of satellites by Starlink above, and other vendors like Amazon only starting to plan their similar programs. That's why early feedback is important - otherwise the sky will be ruined in the best case for decades to come.

One is looking at it, another is polluting it and precluding others from looking at it. Surely you see the difference?

For pure visual observation you might be right, but any sort of amateur astrophotography is already significantly affected and is only going to get worse because 1) it's usually more wide-field than in professional observatories, which significantly increases the chance of Starlink streaks and 2) the ~6.5 magnitude is still a lot brighter than all the interesting deep-sky objects and is only dimmer than stars visible to the human eye.

Yeah, like every start-up clearly did before them (example: Uber). /s

> It’s possible someone could come up with something like that for WebUSB, something that constrains it to something safe.

That sounds like WebSerial and WebHID to me, which don't require similar shenanigans with Zadig on Windows or Linux permission changes, because they allow access to a limited subset of USB device functions.

But that will never cover all the use-cases for USB apps. For those the only choices are not to do anything at all and let closed native executables to continue dominate this space (which gives them unlimited access without even those simplest permission prompts), or to work on WebUSB and encourage devs who do need to interact with such devices over USB to switch to that instead. I don't see 3rd option or how it would be possible in our non-ideal world, and among those two WebUSB still seems like a better idea.

> Limiting it to installed apps still has the problem of users blindly agreeing to something that is fundamentally super dangerous.

Same can be said about native apps. Like with other hazards, in the end it's all about balance - you can't stop users from _ever_ doing stupid things.