re: How I Built A Python Web Framework And Became An Open Source Maintainer VIEW POST

VIEW PARENT COMMENT VIEW FULL DISCUSSION

Absolutely — as some say, async is "all-in".

As you pointed out, I don't think it is specific to how Python does async. It's really two separate views on how things should even run. It does lead to having to basically rebuild everything from scratch just so that it is made non-blocking, which is frankly a rather high barrier to entry.
Luckily in Python, projects like aio-libs are already on their way to building an async equivalent to our otherwise familiar synchronous world. :)

Reminds me of times when I used Kafka for stream processing and I had a hard time interacting with batch-processing systems. Maybe there's a parallel?

  • A batch system is essentially blocking the whole pipeline instead of letting other (streaming) systems consume its changes one after the other.
  • A synchronous function blocks the whole event loop because it doesn't let other (async) functions use the CPU or parts of its outputs while it is running.

Maybe it's this cooperative concurrency model that creates the separation between the sync and async worlds?

I like it though, because I think it's also how we humans work. Our brain is basically a single-threaded concurrent systems that can deal with multiple things at once (to a certain extent) but only ever do one thing at a given time.

Hmm…

"existential questions"

Here we are? :P

Absolutely — as some say, async is "all-in".

Yeah, and that's the divide right there. Async is basically a low level framework. If you adopt it, everything has to be modeled after it. The same way some people criticize some frameworks because they model your application instead of the other way around. Just food for thought.

Luckily in Python, projects like aio-libs are already on their way to building an async equivalent to our otherwise familiar synchronous world. :)

A part of me rejoices, another part of me wonders why we're reimplementing everything from scratch for the nth time :-D

I like it though, because I think it's also how we humans work. Our brain is basically a single-threaded concurrent systems that can deal with multiple things at once (to a certain extent) but only ever do one thing at a given time.

But is it truly? :-) Could it be a bunch of communicating sequential processes instead?

But is it truly? :-) Could it be a bunch of communicating sequential processes instead?

I think it kind of is at a physiological/unconscious level. But I know that's not how my conscious self works. 😁

code of conduct - report abuse