r/erlang • u/AllYouCanAlex • Aug 14 '12
r/erlang • u/nathandigriz • Oct 07 '15
5 Reasons that Learning Erlang is Hard
r/erlang • u/WindowFit3080 • Feb 13 '23
Looking for Erlang coding tutor. $30/hour
I am talking the online "concept of programming langue" class in college. I have several labs that require me to write code in Erlang. I am looking for an Erlang expert to help with the coding. I am willing to pay 30 dollars per hour.
r/erlang • u/HocusLocus • Sep 16 '18
Erlang a lang a lang lang
Ericsson Calling!
Speak the Erlang now
Seattle boys say Wha? Penguin Girls say Wha-What [x2]
Use Erlang Erlang Erlang, Ga la ga la ga la Land ga Lang ga Lang
Con-currency get you down?
Stack em flat, get down get down
Too late you down D-down D-down D-down
Ta na ta na ta na Ta na ta na ta
Bench mark a-blaze Erlang a lang a lang lang
Eager evaluation Erlang a lang a lang lang
Single assignment Erlang a lang a lang lang
Dynamic typing Erlang a lang a lang lang
Who the hell is huntin' you?
Distributed, fault-tolerant,
In the BMW
How the hell they find you?
hot swapping,
Feds gonna hire you
non-stop applications
Pull the strings on the hood
soft-real-time
concurrency explicit
message passing, Erlang a lang a lang lang
Nah explicit locks Erlang a lang a lang lang
open source Erlang a lang a lang lang.
CHORUS:
fib(1) -> 1; % Yah yah heeeeey
fib(2) -> 1; % Oh oh ee yo ee yo
fib(N) -> fib(N - 2) + fib(N - 1). % Yah yah hey.
r/erlang • u/ezoe • Jan 18 '20
Why Erlang did not add some new familiar syntax sugars?
I'm currently learning Erlang and I can't stop thinking about the title.
Erlang could add some familiar, I mean from the perspective of majority of the programming languages, obvious syntax sugars along side with existing syntax. It could be possible without breaking the backward compatibility. It could also help the beginners greatly. I can live without it but it helps a lot.
Now the exact such new syntax idea is a matter of taste, but I can safely say that one example is that some of the comparison operators, namely, !=, <=, ===, !==, correspond to /=, =<, =:=, =/=, could be added without breaking backward compatibility nor introducing syntax ambiguity.
The invention of Elixir, thus causing the dividing of users, could be avoided if the Erlang gradually added up these small but familiar syntax sugars for the majority of average programmers while keeping backward compatibility.
Why is it?
r/erlang • u/Forsaken-Meet-4949 • Feb 08 '26
Unified LLM handlers - Claude, OpenAI, Mistral, Ollama
Hey everyone,
I've been working with LLMs in Erlang and wanted a consistent interface across different providers. So I built a family of handler libraries:
**Core handlers:**
- [`ollama_handler`](https://hex.pm/packages/ollama_handler) - Ollama (local models)
- [`openai_handler`](https://hex.pm/packages/openai_handler) - OpenAI API
- [`claude_handler`](https://hex.pm/packages/claude_handler) - Anthropic Claude
- [`mistral_handler`](https://hex.pm/packages/mistral_handler) - Mistral AI
**Built on top (examples using Ollama):**
- [`ollama_translator`](https://hex.pm/packages/ollama_translator) - Text translation
- [`ollama_summarizer`](https://hex.pm/packages/ollama_summarizer) - Web/HTML summarization
**Why I built this:**
I started with Ollama (for local/private LLM usage) in June 2025 and built translator/summarizer tools on top. The pattern worked well, so I extended it to cloud providers using the same API design - same simplicity, same patterns, different backends.
**Quick example (Ollama):**
```erlang
% Start the handler
ollama_handler:start(),
% Generate text
{ok, Response} = ollama_handler:generate(<<"llama2">>, <<"Explain quantum computing">>),
% Translate text
{ok, Translation} = ollama_translator:translate(<<"Hello world">>, <<"fr">>),
% Summarize a webpage
{ok, Summary} = ollama_summarizer:summarize_url(<<"https://example.com">>).
```
All handlers follow the same pattern - just swap `ollama_handler` for `openai_handler`, `claude_handler`, or `mistral_handler`.
**Current state:**
- Ollama ecosystem is mature (~400 downloads each for translator/summarizer)
- Cloud provider handlers are new (published Jan 2026)
- All use the same dependency: `jsone` for JSON, `wade` for HTTP
**Looking for:**
- Feedback on the API design
- Ideas for additional utilities (like translator/summarizer but for other providers)
- Use cases I haven't thought of
GitHub repos: https://github.com/roquess
Thoughts? Is this useful or am I reinventing the wheel?
r/erlang • u/[deleted] • Nov 08 '25
EEP 79 may be the end of Erlang for me
https://github.com/erlang/eep/pull/81
I see the point, and I am not a fan.
I really loved the dynamism of Erlang.
I love to be able to explore data using list and maps.
I am not even a fan of records TBH.
Not a fan of Elixir structs. Not a fan of "private" "protected" and so on...
OTOH: I am sure that if they want it, it means they need it, and that's a thing I love about the OTP team: pragmatism over philosophy.
For my personal taste though: goodbye Erlang, it's been great fun. Welcome Clojure.
r/erlang • u/erlangsolutions • Nov 21 '19
The 4 key advantages of Erlang and Elixir for blockchain.
When researching and developing their framework, the engineers at ArcBlock compared the popular programming languages in the blockchain community.
They found Erlang offered four key benefits that are fundamental to delivering on the promise of blockchain technology. Discover the benefits, and how they are being utilised by ArcBlock in their latest guest blog.
r/erlang • u/Chawki_ • Jan 18 '19
Which Elixir framework will help me to build a web chat app?
r/erlang • u/vive-la-liberte • Jan 14 '16
Erlang/OTP is the real OTP
The Erlang OTP -- Open Telecom Platform -- is familiar to probably all readers of this subreddit. You might, however, not know that OTP is also an acronym outside of the world of Erlang, meaning "One True Pairing" -- a couple "made for each other".
Since Erlang and Erlang Open Telecom Platform are developed together, I think it is fair to say that Erlang/OTP is the One True Pairing, if you get what I mean :)