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.

  • macniel@feddit.de
    7·
    7 months ago

    its a good idea to be as non blocking as possible especially on time and resource consuming tasks like IO, cryptography, …

    just use await in an async function.

    • EthanOPEnglish
      42·
      7 months ago

      just use await in an async function.

      Sure, I’ll just put await and async everywhere. Oh wait, I can’t. A constructor can’t be async so now I need to restructure my code to use async factories instead of constructors. Wonderful…

      • vzq@lemmy.blahaj.zone
        3·
        7 months ago

        A constructor can’t be async so now I need to restructure my code to use async factories instead of constructors

        It sounds like you’re trying to do OOD/OOP. In js that’s usually not the way to go. You might want to restructure into a more functional architecture anyway.

      • macniel@feddit.de
        2·
        7 months ago

        Sounds like an architectural issue to begin with. A constructor shouldn’t do the heavy lifting to begin with.

        • EthanOPEnglish
          13·
          7 months ago

          You consider calculating the hash of a few bytes to be heavy lifting?

          • macniel@feddit.de
            41·
            7 months ago

            The API doesn’t restrict the amount of bytes to be hashed. So yeah it’s still heavy lifting.

            Trigger a loading event after the constructor is finished that the view model takes to calculate your hash.