There's a lot of trend now like "oh concurrency isn't bad if you have the right language", but those only help with specific cases, the general case is still miserable Concurrency → nondeterminism → multiple possible program behaviors → bugs
-
-
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
If your code is pure then there's no need to specify ordering beyond data dependencies
-
If your code is 100% pure then I'm never receiving my package, am I
- Još 1 odgovor
Novi razgovor -
-
-
I saw this being mentioned in the Out of the Tar Pit paper as an example of something that doesn't matter being specified in the source code. Reminds of the C/C++ semantics in which function argument expressions can be executed in any order the compiler feels like.
-
I'd say, pulling out of my butt, that there are more cases where {people think sequentiality doesn't matter but it does} than {think sequentiality doesn't matter and it actually doesn't}
Kraj razgovora
Novi razgovor -
-
-
If I had to write the sequential equivalent of my last SQL query I’d almost certainly get it wrong. Isn’t that what “out of the tar pit” is on about?
-
Spacial vs Temporal OOtTP is talking about _spacial_ reasoning. Much of modern programming is _temporal_ reasoning. I assume what
@hillelogram is talking about concurrency models (e.g. promises, CSP, actors), which are rooted in temporal reasoning. - Još 2 druga odgovora
Novi razgovor -
-
-
whatever dude I enjoy reasoning through all possible execution orders. It's like my favorite sunday afternoon activity.https://twitter.com/hillelogram/status/1188489583140446208 …
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
If a pure subset of the code is concurrent, I wouldn’t even really call it concurrency, just possibly parallelism, since the order cannot have any effect on the outcome. Laziness is a form of concurrency, since the order is (locally) unspecified, but no one calls it that.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
This is the most frustrating aspect of working with Node. The cost of concurrency is found in trying to debug. The stack traces for normal errors are useless (it's a little better now); and for perf regressions it's not clear that you're spawning 1000s of db connections
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.