Ever wondered what type-safe, massively concurrent functional\nprogramming could look like? Join me on a journey from Erlang to OCaml\nand back again.\n\nWe\u2019ll learn about Caramel \U0001f36c \u2013\nan experiment in bringing type-safety for the Erlang VM. Caramel was\nborn out of the question: why is Erlang hard to type? \u2013 and as it\nturns out, it is not! If you restrict it enough. So much so that what\nyou end up with is\u2026OCaml?\n\nOn the flip side, the new algebraic effects and multicore capabilities\nof OCaml 5 open the possibility of new execution models. How far could\nwe take them? Could we inject Erlang\u2019s famed concurrency model into\nOCaml?\n\nRiot \U0001f32a\ufe0f is an actor-model runtime\nfor OCaml 5 that brings multi-core scheduling and lightweight\nprocesses, communicating via message passing.\n\nKey Takeaways\n\n_ Learn more about how type safety and supervision trees make for the\nultimate reliability stack\n- Understand the convergence of Erlang and OCaml\n- Get started writing Type-safe actor systems in OCaml with Riot\n\t\n\n\n\t\nabout this event: https://bobkonf.de/2024/ostera.html