every layer of your stack must be implemented with asyncio in mind
Most asynchronous apps are developed that way regardless of language.
It sounds like he's mad that old code isn't directly compatible with new code. He is also mad that other developers aren't making it easy enough for him fast enough. Sounds to me like this guy should just avoid trying to write asynchronous code, because it's clearly too hard for him. Or switch to C# and let Visual Studio do the work for him lol.
I personally love async/cocurrent/parallel code. Python's asyncio model does suck. It sucks for many of the reasons he outlines. My personal gripe is that debugging is painful, error prone, tedious, and just generally full of suck. None of these are generally issues with languages which provide first order support for async. With Python, async is grafted on and it's created as a bastard library support with very low level support provided via async and await.
I personally love Python and the only "feature" I actually hate about it is asyncio. I've reached the point where I will no longer do any new project with Python's asyncio. It just sucks too much and is a second class graft.
That said, you might well be right, but I also offer, IMOHO, there is much legitimate ground to claim Python's asyncio is a terrible experience unmatched in any other language I've used which supports async/await.
Python's asyncio model does suck.
I've personally never used it. I've never had the need to write async code in python. I would much rather use Rust or Go for that. Or if I felt like typing 40 lines of code to open a file, I could use Java lol. My point is and IMO he should use a language more suited to what he wants to achieve. Python shouldn't be in anyones top 5 for asynchronous/parallel/concurrent coding. There are better languages...
(post is archived)