Why do threads have to block at the OS? I wonder if the theory behind that might be touched on in Hans J. Boehm's 2004 paper titled "Threads Cannot be Implemented as a Library". I haven't read the paper in a long time, so I'm not sure, but I recall that he outlines many of the reasons you need compiler and kernel support for threading without running into unexpected behavior.
The whole purpose of the talk was running a blocking code in threads, so they don't block. If you involve generators, you already intent not to block, that's why David used pure while loop.
David's talks makes so much of motivation for me as an software developer
Why do threads have to block at the OS? I wonder if the theory behind that might be touched on in Hans J. Boehm's 2004 paper titled "Threads Cannot be Implemented as a Library". I haven't read the paper in a long time, so I'm not sure, but I recall that he outlines many of the reasons you need compiler and kernel support for threading without running into unexpected behavior.
Cool video, as allways! :)
really interesting things
I wish this simple API will be implemented over the Python subinterpreter system...
not to start the flamewar on 572 (30:00), but anything of the form while (x := y()): is really better expressed as a generator...
Not really sure where that outrage came from. Not something i'd use every day but i really could have used it in a few hairy list comprehensions.
The whole purpose of the talk was running a blocking code in threads, so they don't block. If you involve generators, you already intent not to block, that's why David used pure while loop.