Skip to content
0:00 / 0:00

#erlang#joearmstrong#robertvirding

Erlang: The Movie (Fixed Audio)

CH1LLW4VE

563 subscribers • 1 video on Hallway

YouTube
  • Recommended by 2 people: 2 on Hacker News.
  • Presented by Joe Armstrong, Robert Virding, and Mike Williams, co-creators of Erlang

Beginner. No background in the topic needed.

42K views9 years ago2 recommendations

Programming languagesHistory and cultureElixir and ErlangFault tolerance and failureHistory of computing

The creators of Erlang demonstrate the language's fault tolerance, concurrency, and live-system update capabilities in a classic short film.

The uploader added no description.

Why it's here

2 people recommend this

What people say. Highly recommended as a classic, charming, and concise demonstration of Erlang's fault tolerance and concurrency.

riobardon Hacker News • Recommends

On “Goodbye Joe”

Fred probably forgot to mention it, but Joe, Mike, and Robert starred in a short film Erlang: The Movie , a very fine and concise demonstration of fault-tolerance of Erlang. The film has some magic power that I cannot describe but made me watching it over and over again. YouTube link to the film with fixed audio: link to this video

ashton314on Hacker News • Recommends

On “Why Erlang?”

This is almost certainly a reference to Erlang: The Movie 1 which is the most glorious 11 minutes of some programmers explaining how their creation works you will ever see. In the video, the three call each other to demonstrate what happens real-time in an Erlang system. For the impatient, the telephone conversation starts at about minute 3. 1: link to this video

u/intercaeterapress any keyin r/elixir • Mentions

On “Elixir was born from greatness”

You mean Erlang the Movie?

u/flummox1234in r/elixir • Mentions

On “Have you migrated to or from Scala?”

> From what I've read, Elixir's (and Erlang before it) philosophy is to "let it crash". This is more about how to handle faults. Think bad packets in a phone system. link to this video Not just letting your app crash with bad data. In erlang/elixir everything is a supervised process (actor pattern), so it's usually just easier just to retry the thing than writing massive amounts of guard code code to handle any outcome.

rkangelon Hacker News • Mentions

On “The unreasonable effectiveness of declarative programming”

Interestingly, if you watch the Erlang: The Movie ( link to this video ) they use the term 'declarative programming' to refer to what we would now call 'functional programming'. It's an interesting way of thinking about it - these sort of declarative interfaces are very simple in languages with first class function support.

ashton314on Hacker News • Mentions

On “Why Erlang?”

This is the same "movie", but the audio has been fixed to not play out of just the left ear: link to this video

u/flummox1234in r/elixir • Mentions

On “What's special about Erlang and Elixir?”

distributed - you can connect two nodes and load and run code on another node from the first node and leverage the results on the first node, e.g. geographically dispersed nodes running code on a remote master and responding in low latency. Fly.io did a talk on this one. IME there aren't many languages that do this without significant setup or abstraction or additional libraries. Comparing something that is built into a language and is easy to use to kubernetes is laughable. Kubernetes takes a team of people to setup and maintain properly and is a considerable amount of abstractions itself. Erlang's version is just built in for free and ready for you to use. A better comparison might be so…