1,090 karma · joined April 14, 2017
People seem to like monorepos, what problem do you have in mind?
Comparing NumPy to APL it looks that way.
https://analyzethedatanotthedrivel.org/2018/03/31/numpy-anot...
https://qz.com/1043614/this-startup-learned-the-hard-way-tha...
What does this mean? If we know who did them, how are they unsolved?
It's a much simpler model that's just as powerful, and makes it easy to get things right. It eliminates the concepts of futures, promises, and awaitables. It has only one way to wait for a task: await it.
For a theoretical explanation of it's "structured concurrency" model see the now-famous essay https://vorpus.org/blog/notes-on-structured-concurrency-or-g...
"Beautiful is better than ugly." Requests is more beautiful than urllib2.
"Simple is better than complex." Trio is simpler than asyncio.
"Readability counts." Python is more readable than C++.
"There should be one-- and preferably only one --obvious way to do it." ''.join(strings), not sum(strings, '').
Note what isn't in the Zen of Python: performance, close-to-the-metal-ness, correctness, portability.
Python often fails to live up to its values, but that doesn't make them meaningless.
For a theoretical take see
https://vorpus.org/blog/notes-on-structured-concurrency-or-g...
To be precise, to wait for a task its actually just await. Theres no ensure_future etc. Trio doesn't have the concept of futures or promises at all, and await f() is treated as a single piece of syntax, so in practice it doesn't have "awaitables" either.