Raymond Hettinger, Keynote on Concurrency, PyBay 2017

preview_player
Показать описание

Рекомендации по теме
Комментарии
Автор

Oh, i see Raymond Hettinger - i press "Like" :-) Thanks for upload!

senpos
Автор

Raymond is a pleasure to watch and listen to, and makes Python awesome.

baconsledge
Автор

I'm a simple man.. I see Raymond Hettinger, I click the video

kennys
Автор

40k views, 1k likes and only 29 comments, most of which are boring.

This is probably one of the most important, relevant, compelling, authentic videos on the subject of
"How to program intelligently"
After 30 years of coding experience I am prepared to go back to square one because I know it makes sense. The stuff at 33.30 "ASYNC is the future...ASYN maxes CPU, Existing code and libraries, ASYNC means you will have to re-tool..." is pure gold.

simonmasters
Автор

One of the things I liked from "The Pragmatic Programmer" about concurrency was that he also says that it can make it easier to reason about your problem when you free yourself from certain ordering problems.

PhilippeCarphin
Автор

I looked at this a few months ago as a python newbie...few months later this all makes sense and am excited to make the complete transfer to async with my future projects. lots of web app / automation ideas

DivineZeal
Автор

when he said an easy problem even for high school students. I learnt my first for loop when I was 25 and fell in love with programming.

willdg
Автор

What a wonderful and insightful orator and educator.

nuraortap
Автор

What an excellent talk. I wish they had let him delve into the detail of that last piece of code.

saadistik
Автор

Just brilliant!!! He just captured my attention the whole time.

KurzedMetal
Автор

This craziness is how I came to understand why functional programming has value.

pablo_brianese
Автор

From what I got out of the talk, the difference between threads and async/await for existing codebases comes down to these two alternatives:
- changing all the bits of code that could leave shared scopes or output in an inconsistent state if other tasks interrupt them, or
- changing the bits that would ‘block’ other tasks by doing I/O or holding the CPU for so long that it feels like ‘it hangs’.
The message repeated in the talk, then, is that the former is easier, since the changes just involve wrapping the access to shared state/effects with locks on some convenient level. In the async/await version, they would usually require diving all the way down the call graph and replacing the I/O call, or the entire library call it's hard-coded in.
But isn't it much easier to iteratively _find_ idly waiting I/O calls and other things that cause noticeable slowdowns, than it is to find all places that touch references to the same sets of mutable object attributes until you feel safe that it's correct?

feddeschaeffer
Автор

I still find it supersad that gevent does not get the awareness it deserves, imho. No other language offers the convenience of converting a syncronously written program, threaded or not, cooperatively async - with a single line of code, which patches *all* blocking ops into non blocking, taking care of all the callback handling behind the scenes. This is beautiful.
Example: His test question at 34:45 - we had that, had to stop blocking on a telnet/ssh using threaded framework, partially 3rd party, partially from us, since number of comm. sockets increased into the 100ks - one import gevent + patch and that was it. No other change. Paradise, imho.

armynyus
Автор

Great talk. Great teacher. Distills the lesson for good summary.

nelsonmacy
Автор

Best explanation about differences and use cases!

mateuszsmendowski
Автор

Happened to see this. I learned so much out of it.😮

alexl
Автор

Python is extremely popular in the gaming community . . just not for run time code :D It's used a TON for production pipelines and tool writing

Seebergster
Автор

46:30
...and it happend : airplane, automatic control of flight
(plus non-disciplined / non-experienced devs (=cheap), conflict of interest in auditing and authorizing the new feature, etc.)

Geza_Molnar_
Автор

"How can we make this hard, co we can be paid for it?" quote worth remembering

kw
Автор

"an electonical computer" woah mr fancy pants with his electricity.

morthim
welcome to shbcf.ru