Erlang wears three hats - it’s a language, it’s a platform, and it’s an approach to making software run reliably once it’s in production. Those last two are so interesting I sometimes wonder why those ideas haven’t been ported to every language going. How much work would it be?
This week we’re going to dig right down into that question with Leandro Ostera. He’s been working on Riot - a project to bring the best of Erlang’s runtime system and philosophy to OCaml. But why OCaml? Is it possible to marry together OCaml’s type system with Erlang’s dynamic dispatch systems? And what is it about the recent release of OCaml5 that makes the whole project easier?
–
Leandro’s Blog: https://www.abstractmachines.dev/
Why Typing Erlang is Hard: https://www.abstractmachines.dev/posts/am012-why-typing-erlang-is-hard/)
Riot: https://riot.ml/)
Riot source: https://github.com/riot-ml/riot)
ReasonML: https://reasonml.github.io/)
ReScript: https://rescript-lang.org/)
Leandro on Twitter: https://twitter.com/leostera
Kris on Mastodon: http://mastodon.social/@krisajenkins
Kris on LinkedIn: https://www.linkedin.com/in/krisjenkins/)
Kris on Twitter: https://twitter.com/krisajenkins)
--
#podcast #softwaredevelopment #erlang #ocaml #softwaredesign
