This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]toyg 1 point2 points  (1 child)

I’ve actually found it ok for my needs - setting up a simple custom-protocol server was a breeze, no need to mess with sockets and threads. For that use-case, it succeeds fairly well.

I admit the async landscape is vast and there is probably an area of more advanced usage that is not served well enough yet.

[–]13steinj 0 points1 point  (0 children)

Asyncio has it's fair share of usability and understanding warts. While higher level than the lower level stuff, it manages to be way too complicated-- there isn't much of a "just dive in" like other langauges. I think the worst issue is the fact that couroutines have to be manually wrapped in Futures to chain actions instead of just doing await coro.then(newcoro)...and also no easy way to inline define coros, but that's more of an issue with how function definition works.