I hear a lot of people complain that Gleam is “not OTP.” They’re right. At the time of writing, Gleam still doesn’t have a registry or pubsub. If you ask the Gleam team, they’ll tell you to use external calls — which works, but is a pain to reproduce consistently across projects.
So I wrote Glixir, a library that wraps common OTP patterns in Gleam using Elixir’s battle-tested OTP library. It’s not as type-safe as Gleam, but I needed something production-ready today, not next year.
This lets you:
Use supervisors, GenServers, and pubsub patterns from Gleam.
Stay in Gleam where it makes sense, but drop down to Elixir OTP when you need reliability.
Ship code faster without reinventing OTP on the Gleam side.
Obviously there are trade-offs — you give up some type safety, and it’s not “pure Gleam.” But if you’re trying to build something real, you may find this a useful middle ground.
It's MIT so if you disagree with direction you can fork and do whatever you want.
I hear a lot of people complain that Gleam is “not OTP.” They’re right. At the time of writing, Gleam still doesn’t have a registry or pubsub. If you ask the Gleam team, they’ll tell you to use external calls — which works, but is a pain to reproduce consistently across projects.
So I wrote Glixir, a library that wraps common OTP patterns in Gleam using Elixir’s battle-tested OTP library. It’s not as type-safe as Gleam, but I needed something production-ready today, not next year.
This lets you:
Use supervisors, GenServers, and pubsub patterns from Gleam.
Stay in Gleam where it makes sense, but drop down to Elixir OTP when you need reliability.
Ship code faster without reinventing OTP on the Gleam side.
Obviously there are trade-offs — you give up some type safety, and it’s not “pure Gleam.” But if you’re trying to build something real, you may find this a useful middle ground.
It's MIT so if you disagree with direction you can fork and do whatever you want.