159K views · Apr 9, 2007 · 9:58 · 2 HN recommenders · 6 mentions · discussed 2017–2021
A short film about the Erlang language, showing telecom systems built from lightweight processes and demonstrating hot code swapping. It is an edited version of the original Ericsson video.
Why Hacker News points people here: HN treats it as a classic that shows what Erlang was built for: robust, concurrent telecom systems with live upgrades.
“this is truly a gem”HN comment, 2018
“this is truly a gem”
Great explanation of Erlang's benefits for robust systems
I had never watched Erlang the Movie before, this is truly a gem: this video This is a great way to explain the benefits of Erlang. Anyone who has tried to write robust, distributed systems should immediately see the benefits. Even all of these years later.
“Their original video demo of hot code swapping is also a classic worth checking out”
Classic demo of hot code swapping
Their original video demo of hot code swapping is also a classic worth checking out: this video That got a lot of programmers interested in Erlang ~10yrs ago.
“See also: Erlang The Movie”
Erlang's process-per-call model
Spawning a process for each call / endpoint is how almost every large phone switchboard does it. See also: Erlang The Movie: this video
“This is the original video in its 90s glory”
Original video showing telecom hot code loading
This is the original video in its 90s glory: this video Regardless of where the call is handled, you can't just deploy a new switch in a telecom network, but you still want to upgrade them. This is where you really want hot code loading.
“They made a video way back showcasing Erlang in the setting it was primarily used: telecom systems.”
Erlang showcased in a telecom setting
Hehe, shame this got down voted so much. It's actually a pretty hilarious Erlang joke. They made a video way back showcasing Erlang in the setting it was primarily used: telecom systems. In this video they keep calling and greeting each other. The video can be found here: this video
They should have used Erlang this video I wonder what coused this issue? Dependency issue in Maven? May be they cannot figure out what that Java error means?
