Pipe forward : Using Elixir and F# together
summary
Argues Elixir handles orchestration and concurrency while F# provides static typing and computation; demonstrates concrete interop patterns. Implements f-sharp X via Erlang ports that spawns F# Interactive and exchanges messages (works but currently marshals only strings), serves F#-to-JavaScript with Fable->Phoenix front end (works in the same project), and exercises Phoenix channels and REST from F# clients. Calls for stealing tooling ideas like Elixir doctests and REPL help and for tighter type-aware bridges between the runtimes.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:51The ordinary world
- 2:32Awesome Elixir Awesome F#
- 9:06data without code
- 13:38FORBIDDEN
- 19:57Different VMs, Type Systems, Concurrency Models, Cultural heritage
- 22:59Used together? Shared ecosystem?
- 28:36DO NOT REQUIRE CONSTANT DILIGENCE
- 29:18How do I make them work together?
- 57:15Rabbit
related talks
46mFunctional programming in F# Fad or Fabulous
01h 00mFunctional-first programming with F#
01h 14mFunctional Programming in F#: Fad or Fabulous?
01h 08mWhy Every Day as a Developer Would Be Easier with F#
50mWhat’s New in F# 5.0 & Beyond
01h 01mF# as a Better Python
52mF# in the real world
42mHacking F# in JS ecosystem