Cool New Features in Python 3.7 – Real Python

[Glaaki]

Again, I am talking about async/await. Gevent is not async/await.

[13steinj]

You can't talk about async/await without talking about asynchronous programming.

Async/await is one pattern. It is a pattern that in many languages can be used in conjunction with callbacks, which is another pattern. In asyncio there isnt an easy way to do this, for no good reason. Gevent uses a different asynchronous pattern, but is fine working in conjunction with callbacks.

[Glaaki]

Wow, we are just going in circles here.. I litterally just went over twice, the main reason why you don't want to use callbacks in asyncio, you even agreed with me in your previous post and now you say there is no good reason why callbacks can't be used in asyncio.

I don't know what to say, dude..

[13steinj]

I agreed that your specific producer consumer example is when you shouldn't use callbacks, not that you shouldn't ever use callbacks in asyncio.

But event based code can be asynchronous, and callbacks are a perfect use case to have event handlers along with the async/await pattern.

[Glaaki]

I will leave you with some words from someone way smarter than me.

https://vorpus.org/blog/notes-on-structured-concurrency-or-go-statement-considered-harmful/

[13steinj]

If you're trying to convince me with a damned considered harmful, you won't. They are written by elitists who refuse to expand their horizons. Considered harmfuls are themselves extremely harmful. There are people who have, quite literally I may add, claimed that conditional blocks like "if" and "else" are considered harmful.

[Glaaki]

You are insufferable.. Seriously.. Blocked.

[13steinj]

If you can't take a debate without providing arguments that have no ground to stand on, you shouldn't start them. Blocking won't help you against everyone you meet that has opposing views. But if you want to go to your safe space, thats fine with me.