I think one of the most important technical statements in this comment is this: "even the same design errors (global request/response objects)".
(Note to outsiders: we're not talking globals in the usual sense here, they are very carefully crafted proxies on top of thread-locals that behave like globals, i.e. can be imported at module level, but behave correctly in terms of concurrency.)
As a long-time Flask developer, this is the biggest source of frustration when trying to do anything "frameworky" around Flask (see http://mitsuhiko.pocoo.org/AdvFlaskPatterns.pdf for some technical explanations).
There are a lot of emerging web frameworks in Python-land these last years, hopefully some of them will get the success they deserve.
To displace the current dominant players (arguably: Django, Flask and Pyramid), one needs a paradigm shift, just as Django displaced the dominant player (Zope) in 2005 when "MVC frameworks" became the dominant paradigm, or when Flask and Bottle rode the "microframeworks" wave in 2010.
It's a bit difficult to understand what's going on based only on the slides you've linked; do you have a link to a recording of the talk by any chance?
(Note to outsiders: we're not talking globals in the usual sense here, they are very carefully crafted proxies on top of thread-locals that behave like globals, i.e. can be imported at module level, but behave correctly in terms of concurrency.)
As a long-time Flask developer, this is the biggest source of frustration when trying to do anything "frameworky" around Flask (see http://mitsuhiko.pocoo.org/AdvFlaskPatterns.pdf for some technical explanations).
There are a lot of emerging web frameworks in Python-land these last years, hopefully some of them will get the success they deserve.
To displace the current dominant players (arguably: Django, Flask and Pyramid), one needs a paradigm shift, just as Django displaced the dominant player (Zope) in 2005 when "MVC frameworks" became the dominant paradigm, or when Flask and Bottle rode the "microframeworks" wave in 2010.
This current paradigm shift is probably spelled ASGI. For more read https://dev.to/florimondmanca/introduction-to-asgi-emergence...
BTW: here's a fresh take from a friend who did exactly that last year: https://florimond.dev/blog/articles/2018/12/how-i-built-a-we... (with limited success, despite a lot of talent and dedication).
I'm curious to know which of the "new" (ASGI or not) Python frameworks are using these days.