We have to talk about this Python, Gunicorn, Gevent thing
There&#x27;s a huge amount of technical jargon and sarcasm that makes it hard to see her point.<p>Basically she&#x27;s saying that python async (which the current state of the art implementation uses libuv the same thing driving nodejs and consequently suffers from the same &quot;problems&quot;) doesn&#x27;t have actual concurrency. Computations block and concurrency only happens under a very specific case: IO. One computation can happen at a time with several IO calls in flight and context switching can only happen when an IO call in the computation occurs.<p>She fails to see why this is good:<p>Python async and nodejs do not need concurrency primitives like locks. You cannot have a deadlock happen under this model period. (note I&#x27;m not talking about python threading, I&#x27;m talking about async&#x2F;await)<p>This pattern was designed for simple pipeline programming for webapps where the webapp just does some minor translations and authentication then offloads the actual processing to an external computation engine (usually known as a database). This is where the real processing meat happens but most programmers just deal with this stuff through an API (usually called SQL). It&#x27;s good to not have to deal with locks, mutexes, deadlocks and race conditions in the webapp. This is a huge benefit in terms of managing complexity which she completely discounts.