> They mostly need Celery and Redis because in the Python world concurrency was an afterthought You have an operating system that you can use. You don't really

> They mostly need Celery and Redis because in the Python world concurrency was an afterthought You have an operating system that you can use. You don't really _need_ concurrency when you have a machine that can timeshare amongst processes. That's the world Python was designed for > In most other languages you can get away with just running tasks in the background for a really long time before you need spin up a distributed task queue This is partly true, but not a lot of people do this because you need to persist those tasks unless you want them dropped during a reboot. Same logic goes for entire machines disappearing. You _can_ get by without a distributed system, but you will need to tolerate loss in those scenarios. Those losses are non-trivial for most apps/companies, so it doesn't seem all that practical to me to consider a world without a distributed system (and yes, persisting things in postgres/mysql before they are being worked on is still using a distributed system)