Erlang vs Other Languages

Discussions debate Erlang (and Elixir) strengths in concurrency, fault tolerance, distribution, and scalability compared to languages like Java, Node.js, Go, JVM, and .NET, while addressing its performance limitations.

📉 Falling 0.4x Programming Languages
5,097
Comments
20
Years Active
5
Top Authors
#7946
Topic ID

Activity Over Time

2007
23
2008
111
2009
137
2010
149
2011
191
2012
185
2013
241
2014
341
2015
393
2016
458
2017
408
2018
285
2019
334
2020
323
2021
301
2022
261
2023
456
2024
225
2025
268
2026
7

Keywords

TL CPU scheduling.html RPC BEAM OTP JVM HN ETS SMP erlang elixir concurrency processes node beam otp tolerance language messages

Sample Comments

rodly Dec 21, 2013 View on HN

Can someone give me some real world examples of where Erlang really out does Java/C#/C++/etc?

mm263 Apr 12, 2025 View on HN

I'd appreciate an in-depth write-up about deficiencies you found in Node and how Erlang fixes them

farresito May 19, 2018 View on HN

Erlang is not particularly performant, and it seems like what the top comment is describing requires something faster.

apta Jul 19, 2020 View on HN

What does Erlang offer that the JVM or .NET don't?

toast0 Jan 6, 2019 View on HN

I'm a big fan of Erlang, but I think you can acheive similar things in other languages with queues and workers. Erlang's advantage here is that you can do easily do a worker per client connection, for almost any number of client connections; for data processing queues, the lack of data sharing between processes (threads) strongly pushes you towards writing things in a way that easily scales to multiple queue workers -- you can of course write scalable code in other languages, but it&#x

brightball Nov 24, 2022 View on HN

How are Elixir / Erlang anything but great for concurrency?

lliamander Apr 17, 2020 View on HN

Fair Question!It's not a language oriented at maximum throughput of parallel operations.It is a language that is oriented at providing very low latency (soft real-time) handling of lots of events.When you write in Erlang, you decompose your program into lots (think upwards of millions) of small user-space processes, that communicate using asynchronous messages.One side-effect of this architecture is that your application will scale in performance as you add more cores wit

vezzy-fnord Apr 28, 2015 View on HN

Pretty much everything, honestly. Erlang was built from the start to accommodate massive concurrency and robustness requirements, in particular for telecom switches, but largely applicable to anything.Node's a single-threaded reactor pattern event loop, whereas Erlang/OTP is an SMP-enabled virtual machine with a preemptive scheduler that manages lightweight actors called processes, all isolated from each other with their own stack and heap, that can be cheaply spawned and communicat

josefrichter Oct 21, 2025 View on HN

Isn't this what Erlang/Elixir BEAM is all about?

gautamcgoel Sep 11, 2020 View on HN

Can someone explain what Erlang offers that Go does not? Both have great support for concurrency, but Go has type checking and a more familiar syntax.