|
@FlorianHeigl1 | |||||
|
It should be required that they play through the deadlock empire ( deadlockempire.github.io ) before any attempt to argue about concurrency.
|
||||||
|
||||||
|
Hillel
@hillelogram
|
27. lis |
|
Whenever people say things like "Programmers shouldn't have to write sequential code if it doesn't matter", I'm like NO WHAT ARE YOU DOING
Sequentiality means less concurrency and that's A Good Thing
|
||
|
|
||
|
Hillel
@hillelogram
|
27. lis |
|
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
|
||
|
|
||
|
Hillel
@hillelogram
|
27. lis |
|
Oh my god, this is incredible
|
||
|
|
||
|
on error resume next
@FlorianHeigl1
|
27. lis |
|
Glad you also loved it... There should be more like it
|
||
|
|
||
|
Paulo Renato
@Exadra37
|
28. lis |
|
Well but as far as I am aware you have #programming languages, like #elixir and #erlang, that dont suffer from this deadlock issue, neither they need semaphors.
cc @josevalim
|
||
|
|
||
|
Hillel
@hillelogram
|
28. lis |
|
Elixir and Erlang can suffer from livelock problems though
|
||
|
|
||
|
Wes
@weskerfoot
|
27. lis |
|
greenteapress.com/wp/semaphores/ as well is an excellent introduction to the issues concurrency can bring
|
||
|
|
||
|
Tobias N. Sasse
@tnsasse
|
27. lis |
|
Can we have that for Java please? 😍
|
||
|
|
||
|
Petr Havlak
@petrhavlak
|
28. lis |
|
Wow, didn't know that 😀💪
|
||
|
|
||
|
Francois Armand
@fanf42
|
28. lis |
|
wow, this site is a pearl!
|
||
|
|
||