While at a desk Raúl spends his time doing Elixir stuff but also enjoying getting into rabbit-holes that make him better understand complexity 🌀
He enjoys the nuances of programming but would like programs to tell you more, especially when they go wrong. Gleam does fulfill a bit of that ✨
Otherwise, loves trying out traditional food; sharing evenings with friends; gaming; has a small family with wife, baby and cat 🦦
Gleam is a programming language that makes the case for type safety in the BEAM. Give it a try and you will soon discover that the straightforward syntax and great error messages give you the power to start building your domain logic behind a lovely typed foundation.
It is a great choice for simple finite programs that will not break, but the BEAM offers much more than that… Its process primitive gives us the means to model asynchronous and concurrent work.
Gleam offers a way to represent processes and messages within the type system and uses that to rebuild one of the fundamental abstractions of OTP an Actor. In this talk we’re going to disassemble what makes an Actor and what it takes Gleam to make it work along its type system.
OBJECTIVES: Understand what is a Gleam Actor and how we can map process messages to types.
AUDIENCE: Will briefly go through some of the concepts behind, and Actor and Gleam’s type system, but having familiarity with Erlang’s (or Elixir) GenServer will be useful.