3 ms·
Just because you don't understand the difference between gevent and asyncio, please don't post garbage laundry lists of your flavor of the month stack choices.
by coleifer 7y ago
Just because you don't understand the difference between gevent and asyncio, please don't post garbage laundry lists of your flavor of the month stack choices.
It's an amazing library and a very unique way to write cooperatively-scheduled applications. Best of all it works with existing libraries and doesn't require special "asyncio" implementations from top to bottom. It's not a silver bullet, but don't fool yourself that asyncio is because it's been blessed.
- yowlingcat 7y agoI think I understand the difference between gevent and asyncio pretty well. Moreover, it sounds like you understand the difference between community adoption and not, but you're fighting against community adoption with your own opinion of what is a "garbage laundry list" -- okay. You can say that. But, there's a reason the gevent approach is not what the community settled on. What you call "special" asyncio implementations others would merely call obviously explicit code. Async/await is a powerful syntactic construct. I would never go back to gevent hell after using it.