this post was submitted on 06 Jun 2024
17 points (79.3% liked)

Programming

17377 readers
502 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

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
17
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 6 points 5 months ago* (last edited 5 months ago) (2 children)

Given the nature of JS running only on a single thread. Promises/asynchronity is the only way to keep the browser from locking up.

Thus insisting on any other way is a major flaw in the developer not the language.

[–] vzq@lemmy.blahaj.zone 5 points 5 months ago (1 children)

Thus insisting on any other way is a major flaw in the developer not the language.

I mean, I understand the idea, but this is a pretty asshole way to frame it. I don’t think I deserve that, and certainly OP doesn’t deserve that.

[–] mrkeen@mastodon.social 2 points 5 months ago

@DmMacniel @vzq

> Given the nature of JS running only on a single thread.

No no, I think you found the language flaw.