Why is crypto.subtle.digest designed to return a promise?
Every other system I’ve ever worked with has the signature hash(bytes) => bytes, yet whatever committee designed the Subtle Crypto API decided that the browser version should return a promise. Why? I’ve looked around but I’ve never found any discussion on the motivation behind that.
@DmMacniel @vzq
> Given the nature of JS running only on a single thread.
No no, I think you found the language flaw.