Erlang/OTP
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
4recommend
2warn against
Nov 1, 2025first mention
Sep 12, 2026latest mention
Why people recommend it
“As an Erlang and now gleam developer, I'm continuously grateful for the BEAM's support”
“Erlang/OTP solved this in 1986 for telecom switches that needed 99.999% uptime.”
Runs 8 AI agents for a solo companyon “You hired the AI to write the tests. Of course they …”
Show 2 more
“using the principles from Erlang/OTP”
“The OTP offers a flat/simple architecture”
Caveats and dissent
“OTP is a really roughneck standard library”
Often compared with
Who recommends it in their own words
Threads where it came up
- How I fell in love with Erlang 2 mentions
- A Design Space Exploration of Async/Await 1 mention
- Agentic coding deserves more than a chat box bolted onto VS Code 1 mention
- Phoenix LiveView 1.2 Released 1 mention
- Erlang/OTP 29.0 1 mention
- You hired the AI to write the tests. Of course they pass 1 mention
Also written as Erlang, Erlang OTP. Data: erlang-otp.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 11
“As an Erlang and now gleam developer, I'm continuously grateful for the BEAM's support”
That video is the perfect amount of awkward. I love it.
“It is, since OTP 24 was released in 2021”
“supervisors don't cover all use cases of job control”
“Erlang/OTP solved this in 1986 for telecom switches that needed 99.999% uptime.”
“using the principles from Erlang/OTP”
“I use many of the otp functions in gleam on thr regular”
“Erlang functions won't be optimized. See section 2.3”
“OTP is a really roughneck standard library”
“The OTP offers a flat/simple architecture”
“This document says Erlang processes use 309 words”