Programming

17376 readers

148 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Why is crypto.subtle.digest async? (programming.dev)

submitted 5 months ago by firelizzard@programming.dev to c/programming@programming.dev

16 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] DmMacniel@feddit.de 7 points 5 months ago (1 children)

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.

[–] firelizzard@programming.dev 2 points 5 months ago (2 children)

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 points 5 months ago* (last edited 5 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.

[–] DmMacniel@feddit.de 2 points 5 months ago (1 children)

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

[–] firelizzard@programming.dev -2 points 5 months ago (1 children)

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

[–] DmMacniel@feddit.de 3 points 5 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.