# Elixir vs Python **URL:** \ **Category:** Discussions\ **Tags:** discussion, python, elixir\ **Created:** [September 24, 2019, 11:32am UTC](https://forum.elixirforum.com/t/elixir-vs-python/25619 "2019-09-24T11:32:55Z")\ **Posts on this page:** 1\ **Showing post:** 28
**Author:** ![amnu3387](https://forum.elixirforum.com/letter_avatar_proxy/v4/letter/a/ed8c4c/32.png) [@amnu3387](https://forum.elixirforum.com/u/amnu3387)\ **Post date:** [January 8, 2020, 9:08am UTC](https://forum.elixirforum.com/t/elixir-vs-python/25619/28 "2020-01-08T09:08:05Z")
You also have Erlang’s sys module, so with a pid you can do `:sys.get_state(pid)` and get the actual state, and there’s other functions in sys. You can also always create a specific handler to handle the state inspection (though both sys and handlers require that the server isn’t blocked doing something). I have no horse in the race between elixir/erlang and other languages and sometimes I wonder looking at the code why I prefer to work with elixir/erlang - but in the end it boils down to the actual simplicity - once you have in mind the very basic building blocks everything more or less follows the same structure (supervisor, children (which usually have more children), monitor/link, trap exits or listen for down messages, start-\>do stuff in steps-\>stop) and extending a gen\_server, or gen\_statem to handle new cases, new flows and/or new paths is usually pretty trivial in my experience - the same with adding concurrency to it, limiting the concurrency, etc. Lastly usually if you’ve isolated the servers, changing them to a new independent app is a matter of moving the modules and changing a few lines in the supervision trees. To me it just makes sense. Of course, some things are expensive to do in the beam but since I usually don’t need super fast arrays or anything like that where mutability shines, I’m ok with that. --- _[View the full topic](https://forum.elixirforum.com/t/elixir-vs-python/25619)._