|
|
|
|
|
|
by andy_ppp
3861 days ago
|
|
|
I don't know, I'm starting to run into a lot of difficulties writing a system than manages lots of different processes; I've ended up splitting a lot of these things into APIs now that have a rabbit a between them and the thing looks a lot better. Language level integrated and robust process management/OTP features really are great; you only need to look at something like twisted to see that Python is not a perfect fit for managing this stuff and I'll play with other languages (probably Elixir right now) to see what I can learn. Maybe the original poster is missing the point that having Python ideas added to a functional language would help? Or maybe I should just learn functional programming properly! |
|
|
It's not right to bring just twisted to the discussion, I can give you tornado as completely the opposite, it's beautiful and simple and plays great with the multi-process libraries and asyncio, Python 3, etc.
The concurrency models are just different and it's probably nothing wrong with that, single threaded processing using coroutines inside and talking with other processes by message passing using zmq and not rabbit could be monitored with supervisor another great python tool... they are just different tools for different jobs that in fact work in team better that for each own, Python + Erlang.
My point is that is like comparing a mango with a sunfruit, and again there's nothing wrong with the erlang syntax.
Btw I know rabbit it's build on Erlang but again I think it's not a good Erlang example, you could used cowboy as a better OTP builded Erlang application, and again just a mater of perspective.