Good videos, with context.
Erlang: The Movie

Erlang: The Movie

dawsdesign
2 HN recommenders · discussed 2017–2021
Open YouTube ↗

About this video

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 it appears in the archive

HN treats it as a classic that shows what Erlang was built for: robust, concurrent telecom systems with live upgrades.

AI-generated summary and labels from the source dataset; verify important details against the video. Source & credits.

From the Hacker News discussion

jimbokun · 2018-12 · strong rec

I had never watched Erlang the Movie before, this is truly a gem: [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.

Read original comment ↗
SkyMarshal · 2017-05 · rec

Their original video demo of hot code swapping is also a classic worth checking out: [VIDEO] That got a lot of programmers interested in Erlang ~10yrs ago.

Read original comment ↗
jacquesm · 2019-10 · reference

Spawning a process for each call / endpoint is how almost every large phone switchboard does it. See also: Erlang The Movie: [VIDEO]

Read original comment ↗
dmitriid · 2020-10 · reference

This is the original video in its 90s glory: [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.

Read original comment ↗
probst · 2021-01 · reference

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: [VIDEO]

Read original comment ↗
darkhorn · 2019-06 · joke

They should have used Erlang [VIDEO] I wonder what coused this issue? Dependency issue in Maven? May be they cannot figure out what that Java error means?

Read original comment ↗