Комментарии:
I read 5 articles and it wasn't until I watched this that I had deep understanding of the concept
ОтветитьWhy can't I do web stuff with the multiprocessing library and what is the alternative? Let's say I computer that needs to run a python project that is both a Flask server and also does multiprocessing actions
ОтветитьYou are awesome Miguel, seldom have I seen such complex things explained and put into perspective this easily, take care and god bless you and your family.
Ответитьthanks for sharing
ОтветитьDidn't know Ben Kingsley wrote Python.
ОтветитьAsync doesn't make your code fast. It makes it just less idle
ОтветитьBrilliant analogy!
ОтветитьYou don't really understand something until you can think of a really good analogy to explain it.
Ответить1.25x
ОтветитьI will never forget in my second year of comp sci classes in college (back when comp sci was the only computer class), my instructor told me (the class) that this was not asynchronous programming. And in the same breath that only MS was async. I have never forgotten what an idiot she was.
ОтветитьI felt the chess analogy cleared my confusions here . Thank you so much .
Ответитьmiguel is a legend. i really like how humbly he speaks
Ответить100% the chess example is hands-down the BEST possible example
ОтветитьI fininally understand what Aysnc means. That chart comparing Process vs Thread vs Async is gold!
ОтветитьBrilliant talk!
Ответитьas a chess player i really appreciate the example.
ОтветитьWonderful overview of not only async but the advantages over multiprocess/multithread. It is good point that asyncio is designed to make you write/think in an async way.
Ответитьcouldn't have explain it better :)
ОтветитьIf asynchronous programming is just a style of concurrent programming, what are the other things that come under the umbrella of concurrent programming??? I thought this is the only way to do concurrent programming...
ОтветитьExcellent talk !!!
ОтветитьPlease give this man more time!
ОтветитьThreads arn't really any use if there are CPU bound tasks and hence GIL is an issue, but with async if GIL is not issue you can do concurrent CPU bound tasks, i think its an important he missed mentioning.
ОтветитьThis is how one should teach . That chess example is the best anyone could have given .
ОтветитьAppreciate this channel sharing this very informative content.
ОтветитьGreat talk!
ОтветитьYou rock :)
Ответитьgreat talk, very straightforward as it is.
ОтветитьThanks Miguel.
ОтветитьVery clear explanation !
ОтветитьCan you please share the slides
ОтветитьMiguel Grinberg thanks.
ОтветитьIn summary, asyncio is great when at minimum you need thousands of concurrent executions in a process. Threads work for when you need mere hundreds at maximum, albeit with possible race conditions. Also, threaded programming is different and reasoning about it is different.
ОтветитьThis came up in the next recommended videos, and I wasn't particularly immediately interested in the topic as far as today was concerned (though I did have a todo interest for future review). But once I saw Miguel Grinberg was the speaker, I ponied up for the watch.
ОтветитьAlways a good and clear talk. Thanks Miguel
ОтветитьGreat! Thanks, Miguel.
ОтветитьLove Miguel teaching many years!
ОтветитьReading Miguel's Flask book right now. He's a great writer, and apparently a pretty good speaker as well.
ОтветитьA good talk.
However, the gevent and eventlet examples were mismatched to the preceding "yield from" and "await" examples. Those used a loop to run the functions, which is the natural way to do it as it allows other functions to be also run asyncronously by that loop - hence the 10 call example with 10 hellos, followed by 10 worlds. The gevent and eventlet examples just called each single function in a non asynchronous way.. To be matching, they should have used the corresponding loop from those frameworks to similarly allow 10 versions of those functions to potentially be launched at the same time. The reason I mention this was the point that gevent and greenlet were harder to keep track of, as this omission served no purpose, other than to contrive this point a little.
so simple, but surprisingly good and very informative
ОтветитьThought it was going to be about Flask.
Ответитьvery good talk. clear concepts and examples
ОтветитьVery nice talk, cleared up a bunch of questions I had on asyncio.
Ответить