Is it just me or does the Go community use a different definition of "concurrency" vs "parallelism"? The "standard" one is afaict "parallelism is one way of getting concurrency", whereas Go seems to use it specifically to talk about interleaving.
-
-
Most interesting approaches to parallelism are structured around reducing the likelihood of accidentally working on the same object at the same time ("what would that even mean?!" is sometimes called "undefined behavior" or "UB" in C++ jargon)
-
That was probably too much. Ask away.
-
Just a followup: how does the interleaving happen in the browser? Who/what process handles it? Does the browser delegate it to the OS?
-
The browser controls the JavaScript event loop. The OS scheduler isn't involved.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.