News for hackers. Stuff that matters.

A comment on How to think about `async`/`await` in Rust. Parent comment

Re:How to think about `async`/`await` in Rust by nvy on Wednesday July 05, 2023 @11:54AM (#36602224)
But concurrency is just "single core parallelism" anyways, so this isn't really germane to the discussion.

JS has neither.

[ Parent | on HN ]
Re:How to think about `async`/`await` in Rust by Sinidir on Wednesday July 05, 2023 @04:34PM (#36606725)
Concurrency is not "single core parallelism". Concurrency describes tasks/threads of execution making independent progress of each other. Parallelism describes tasks/threads actually running at the same time.
[ Parent | on HN ]
Re:How to think about `async`/`await` in Rust by nvy on Wednesday July 05, 2023 @08:08PM (#36609089)
>Concurrency is not "single core parallelism"

Of course it is. Concurrency gives the impression to the user that parallel processing is being done, even when it's not. That's why my parents old 386 could render a moving mouse cursor and a progress bar at the same time (usually).

Concurrency lets you do things "in parallel" even if you can't actually do them in parallel.

[ Parent | on HN ]