undefined | Better HN

0 pointskristjansson1y ago0 comments

You don’t? concurrent.futures.ThreadPoolExecutor can get a lot done without touching async code.

0 comments

I am a big advocate for ThreadPoolExecutor. I'm saying it's superior to asyncio. The person I'm responding to was asking why use threads when you can use asyncio instead.

kristjanssonOP1y ago

Ach, I posted before I saw the rest of your thread, apologies.

Totally agree, concurrent.futures strikes a great balance. Enough to get work done, a bit more constrained than threads on their own.

Asyncio is a lot of cud to chew if you just want a background task in an otherwise sync application

j / k navigate · click thread line to collapse

0 comments

BugsJustFindMe1y ago

I am a big advocate for ThreadPoolExecutor. I'm saying it's superior to asyncio. The person I'm responding to was asking why use threads when you can use asyncio instead.

kristjanssonOP1y ago

Ach, I posted before I saw the rest of your thread, apologies.

Totally agree, concurrent.futures strikes a great balance. Enough to get work done, a bit more constrained than threads on their own.

Asyncio is a lot of cud to chew if you just want a background task in an otherwise sync application

j / k navigate · click thread line to collapse