3 ms·
1. twisted seems to have made some design decisions only to support windows. A quick glance at the tulip api shows a clear separation of these models (i.e. pro
by penguindev 13y ago
1. twisted seems to have made some design decisions only to support windows. A quick glance at the tulip api shows a clear separation of these models (i.e. proactor vs reactor)
2. the new 'yield from' (which I think is a more awkward name than 'await') is much more pythonic/readable than callbacks.
3. they're trying to standardize on an event loop interface (like they standardized on WSGI, I believe)
I haven't used twisted, but coworkers that tried to prototype something in it on Linux got sucked into a tarpit of no return, and wasted a huge amount of time. (they did not try the build a simple prototype and throw it away trick, unfortunately)
So no, twisted is not cursed, people are either happily using it or figuring out how to write something more intuitive, like every other piece of software on the planet.