4 ms·

Race conditions are in the nature of concurrent code. Not just parallel code. Take go, use gomaxprocs and set it to 1. Spawn a bunch of goroutines that share m

Race conditions are in the nature of concurrent code. Not just parallel code. Take go, use gomaxprocs and set it to 1. Spawn a bunch of goroutines that share memory. And easily you'll have race conditions if you're not careful.

piterrro 6y ago
I didnt say race conditions are impossible in Nodejs. Just highlighted that good program engineering is enough to avoid it and programmers should do that in the first place.
- aaomidi 6y ago
  Sure but at the same time there is a reason synchronization primitives exist. Readability of code > everything else.
  - piterrro 6y ago
    Nodejs doesn't have synchronization primitives, just because you use Promise and assign it to variable "mutex" doesn't make it any more real
    - emteycz 6y ago
      What do you think is the real thing? It's also a value in a memory cell.
      - aaomidi 6y ago
        Yup :) https://github.com/golang/go/blob/master/src/sync/mutex.go https://github.com/golang/go/blob/master/src/sync/mutex.go You can easily see what Go does here. It's not magic.
- deleted 6y ago
  [deleted]
- dboreham 6y ago
  It would be better if I had the time today to refute this in detail, because it's important that others reading this thread know this assertion is false, but...it's false.
- cphoover 6y ago
  Agreed Over the past 10 years, I've done async code to coordinate lots of different concurrent tasks in JS, never once needed a the use of a mutex.