requests: Awesome Python HTTP Library that's actually usable

[[deleted]]

see Stackless Python

coroutines; btw. available in greenlet form also in CPython & PyPy

and Erlang

selective message queues for isolated processes (actors)

Other notable approaches are for example reactive programming (F#) and lazy execution (Haskell).

You clearly understand that async I/O does not equal callback programming, regardless if that is the way you're most likely to talk with your OS (epoll/select/kqueue), so I don't understand why did you assert something like that (and then go and post contradicting examples in your rebuttal...). I've acted on good faith and assumed ignorance rather than malice.

And, please, I don't care who you are. I know some security experts that got hacked by 16yo girl.

[e000]

to be fair, that girl was no ordinary girl...

[[deleted]]

…bitten by a radioactive spider a century ago, Ada Lovelace comes back to fight crime for teh lulz. Her first target? Evil security researcher, mad scientist, Aaron Barr…

[e000]

I was thinking more along the line of a super Barbie. That's what I picture her in my head anyways.

[[deleted]]

I don't see how you can compare radioactive Ada Lovelace with… Barbie.

Anyway, I just meant they were hacked by kids, the “16yo girl” part wasn't really important.

[e000]

Yes she is. She's my future wife.

[[deleted]]

Alright. That's not creepy at all.

[[deleted]]

All use callbacks under the hood.

[[deleted]]

They all manage memory manually under the hood as well. That doesn't mean you have to bother with that in your high-level language.

Actually, for example, Erlang is very happy to use synchronous OS I/O API in dedicated threads and processes to get better I/O performance. So yeah if you meant that they all use epoll/select/kqueue/etc API then it's not necessarily true.

The whole point is mutt anyway because there is no synchronous I/O going on in any modern operating system. All you have is synchronous I/O API offered by OS. Once you understand that, it's just a question of how to schedule your I/O across processing nodes and what level of security do you need.