Erlang vs Python: What are the differences?
What is Erlang? A programming language used to build massively scalable soft real-time systems with requirements on high availability. Some of Erlang's uses are in telecoms, banking, e-commerce, computer telephony and instant messaging. Erlang's runtime system has built-in support for concurrency, distribution and fault tolerance. OTP is set of Erlang libraries and design principles providing middle-ware to develop these systems.
What is Python? A clear and powerful object-oriented programming language, comparable to Perl, Ruby, Scheme, or Java. Python is a general purpose programming language created by Guido Van Rossum. Python is most praised for its elegant syntax and readable code, if you are just beginning your programming career python suits you best.
Erlang and Python belong to "Languages" category of the tech stack.
"Real time, distributed applications" is the top reason why over 49 developers like Erlang, while over 1022 developers mention "Great libraries" as the leading cause for choosing Python.
Erlang and Python are both open source tools. It seems that Python with 25.3K GitHub stars and 10.5K forks on GitHub has more adoption than Erlang with 7.74K GitHub stars and 2.1K GitHub forks.
According to the StackShare community, Python has a broader approval, being mentioned in 2826 company stacks & 3632 developers stacks; compared to Erlang, which is listed in 70 company stacks and 47 developer stacks.
What is Erlang?
What is Python?
Want advice about which of these to choose?Ask the StackShare community!
What are the cons of using Erlang?
What tools integrate with Erlang?
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than right now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
To me, this is by far the best programming language. Why? Because it’s the only language that really got me going after trying to get into programming with Java for a while. Python is powerful, easy to learn, and gets you to unsderstand other languages more once you understand it. Did I state I love the python language? Well, I do..
Backend server for analysis of image samples from iPhone microscope lens. Chose this because of familiarity. The number one thing that I've learned at hackathons is that work exclusively with what you're 100% comfortable with. I use Python extensively at my day job at Wit.ai, so it was the obvious choice for the bulk of my coding.
been a pythoner for around 7 years, maybe longer. quite adept at it, and love using the higher constructs like decorators. was my goto scripting language until i fell in love with clojure. python's also the goto for most vfx studios and great for the machine learning. numpy and pyqt for the win.