5 ms·
I still prefer Twisted, it feels more natural to me. But this is something that one cannot say aloud in many Python circles.
by 991821911 10y ago
I still prefer Twisted, it feels more natural to me. But this is something that one cannot say aloud in many Python circles.
- rgacote 10y agoLong-time Twisted user (and lover) here. Lots of what we build are fairly web-transaction data translators (http to http or http to db APIs). I find that async.io, by avoiding callbacks, allows us to create a more classical-looking code structure. It works for us. That being said: a) the Twisted environment is extremely robust and battle tested. b) I know that after six months of writing async.io code I'm still just tipping my toe into the capabilities and have yet to fully wrap my head around the details. Would love to see one of those single-topic O'Reilly books take a deep dive into async.io details.
- bogomipz 10y ago>"But this is something that one cannot say aloud in many Python circles" Can you explain why this is? What's the central issue?
- X86BSD 10y agoTwisted ROCKED. I remember when it came out everyone I knew thought it was pretty kick ass, at least those who developed in Python. Did something happen that it's now fallen out of favor?
- the_mitsuhiko 10y agoTwisted is still popular. Problem is that in 2.x the async ecosystems do not work together and many things might not exist everywhere. Twisted seems to have lost a bit of ground with newer things like Kafka etc.
- rspeer 10y agoBy now, people expect libraries to have thorough documentation on the Web, not just an O'Reilly book. The fact that the port of Twisted to Python 3 is slow-going, and far from complete, also gives the suggestion that there are corners of the code that developers don't even understand anymore.
- dbcurtis 10y agoPffft. Twisted core devs have embraced asyncio and have made Twisted play nice with asyncio. Do what makes sense.