 |
| What Color Is Your Function? (2015) (journal.stuffwithstuff.com) | ||
| recommended by 2 users | 2020 | 106 points by chrfrasco | concurrency | original thread | | ||
| 2 users recommended this thread. What they said: |
| d33 Aug 4, 2020 | on: Django 3.1 | context |
|
3np Jul 5, 2023 | on: How to think about `async`/`await` in Rust | context
Your rant reminded me of this classic post, which I believe shares your views but from different reasoning. https://journal.stuffwithstuff.com/2015/02/01/what-color-is-... https://news.ycombinator.com/item?id=36597229 (fresh repost) Discussed previously: |
| Also recommended by people who recommended this: | ||
| 1. | What Color Is Your Function? (journal.stuffwithstuff.com) | |
| recommended by 2 users | 2015 | 410 points by jashkenas | original thread | | ||
| 2. | What Color is Your Function? (2015) (journal.stuffwithstuff.com) | |
| recommended by 1 user | 2018 | 109 points by thinkloop | original thread | | ||
I feel like it's too little too late, but the idea is good. There's an obligatory reading:
https://news.ycombinator.com/item?id=23218782
Five times later, there are some new frameworks, but much of the ecosystem is still sync-only. This is actually one of the things that is pushing me towards Go lately. Python just doesn't seem to mature fast enough and tools heavily disagree on conventions.