> On Aug 8, 2016, at 4:45 AM, Cory Benfield <c...@lukasa.co.uk> wrote: >> > > The first is that, by sheer good luck, I’ve managed to tap into a zeitgeist > and be in the right time at the right place to deliver this message. Dave > Beazley’s work on curio here is helping, because of curio’s sheer > incompatibility with the other event loop approaches, which means that his > work and mine have a nice symbiosis. Nathaniel and I have managed to give him > the building blocks to demonstrate curio’s effectiveness without him needing > to be an expert in HTTP. >
Chiming in on the "zeitgeist" comment for a moment, I've wondered for a long time why Python can't reinvent itself in the area of I/O (and maybe systems programming generally). Honestly, I feel like a whole lot of time has been burned up thinking about Python 2/3 compatibility instead of looking forward with futuristic new projects and ideas. Perhaps "async/await" serves as a catalyst to rethink some of these things. A lot of my work with async/await is really focused on exploring the API space with it--well, at least seeing how much I can twist that part of the language in diabolical ways. The protocol issue is real though. Sure, I could probably bang out a passable HTTP/0.9 protocol in an afternoon, but try to tackle something modern like HTTP/2? No way. I'm totally out of my element with something like that. Having an I/O-free implementation of it is cool. It would be pretty neat to have something like that for various other things too (Redis, MySQL, postgres, ZeroMQ, etc.). Cheers, Dave _______________________________________________ Async-sig mailing list Async-sig@python.org https://mail.python.org/mailman/listinfo/async-sig Code of Conduct: https://www.python.org/psf/codeofconduct/
