undefined | Better HN

0 pointsbriansmith7y ago0 comments

We are continuing the project of replacing C code with Rust code in ring. The pace of that effort is mostly a function of how much work time I have available to spend on ring.

Day-to-day ring development happens on Windows and it was designed to "just work" on Windows (as well as Linux, macOS, Android, iOS, and other supported target operating systems). We did a huge amount of work to make the build system fully automatic to enable this, and we have a pretty extensive CI mechanism to make sure everything "just works" as much as we can.

As for WebAssembly, I'm looking forward to something like https://pdfs.semanticscholar.org/3887/6d86e5e7851181efc9ed3b....

However, you should probably use the WebCrypto API in a web app if at all possible, instead of a wasm crypto library. Unfortunately the WebCrypto API is 100% asynchronous whereas almost every other crypto API is 100% synchronous so that's easier said than done. Really browsers should add a synchronous WebCrypto API; then crypto libraries can transparently delegate to it when targetting wasm.

0 comments

amenghra7y ago

async/await makes it pretty easy to take an async library and use it in a synchronous context.

eridius7y ago

No it doesn't. await doesn't make asynchronous functions synchronous. It just changes how you write the code, not how the code itself works. Notably, await can only be used from inside an async function.

coldtea7y ago

Once you go asynchronous (e.g. call an async function, wait for a promise) you can never go back to a synchronous context in that chain of code.

async just makes asynchronous look like a synchronous code, but it's still event-based and async.

j / k navigate · click thread line to collapse