4 ms·
Asyncio detractors have been drowned in a stream of assurances that, really, it's not that bad. Obviously it is, or this wouldn't be post #800 that promises to
by dilandau 6y ago
Asyncio detractors have been drowned in a stream of assurances that, really, it's not that bad.
Obviously it is, or this wouldn't be post #800 that promises to finally make asyncio clear to newcomers.
Twisted sucks. It was a joke. Now it's been tacitly blessed to the point you can sprinkle the `async` keyword all over the place. Good luck. I hope you don't forget about any spots.
I truly think part of the reason Guido left is because he couldn't defend this shit.
- nessunodoro 6y agoNot to stoke the flame, but I never used Twisted, where did it fail?
- carapace 6y agoBad docs. Everything else about it is solid as hell. Pathlib comes from Twisted IIRC.
- birdyrooster 6y agoYes Twisted had its draw backs but that was well over 15 years ago. Async io is literally like a couple keywords and a library with a few classes you will use for everything. No more callback/errback chaining or function decorators every single method for inline callbacks. No one in these comments are offering any palatable alternatives. A compiled language with no OO is not a replacement for Python's Asyncio.