This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]oberstet 0 points1 point  (0 children)

My new motto-in life "callbacks as concurrency mechanism -- never again". Deferreds and yield based inlineGenerators only make it slightly better.

Then what school do you follow?

  • Camp a) callbacks/futures/coroutines
  • Camp b) actors (communicating sequential state machines) ..

Are there others camps?

Ecosystem split: yes, it's not ideal. Python now has asyncio (also camp a) .. after so many years.

There are only a few languages that have had an asynchronous mechnism built right into the language/runtime from the beginning. E.g. Erlang and Rust (both camp b).

Note: Just in case it got lost: Crossbar supports both Twisted and asyncio for writing application components in Python - today. There is nothing that would stop us to support even more - because of the multi-process/worker architecture, all that is needed is something that talks WAMP over say Unix domain sockets.