After nearly a decade of writing our software in Erlang, our codebases have started getting unwieldy despite our best efforts to manage this through other disciplinary methods. (That and dialyzer, but there are limits!)

So we did what any sensible company would do, and hired "the Purerl guy" and set about working out how we could use the Purescript to Erlang compiler he'd written to help us with this. To that end since, we have already shipped two products and quietly open sourced a selection of the libraries we have built on top of Purerl to support those endeavours.

In this session we'll start by looking at the super happy path (our ideal world) for end-to-end Purescript before going into detail on how some of it is implemented, the weak spots and pitfalls currently present and some of the huge hacks that are possible when using Purescript FFI to bind against "native Erlang" libraries.

THIS TALK IN THREE WORDS

Erlang

Purescript

OTP

OBJECTIVES

To get people excited about Purescript on the BEAM

TARGET AUDIENCE

Erlang developers, Purescript developers