Marko Rauhamaa <ma...@pacujo.net> writes: > Note that neither the multithreading model (which I dislike) nor the > callback hell (which I like) suffer from this problem.
There are some runtimes (GHC and Erlang) where everything is nonblocking under the covers, which lets even the asyncs be swept under the rug. Similarly with some low-tech cooperative multitaskers, say in Forth. When you've got a mixture of blocking and nonblocking, it becomes a mess. -- https://mail.python.org/mailman/listinfo/python-list
