ReasonConf 2018
as the organisers put it
Reason is the next big thing and it is time to bring the community together. Come and learn about the language and get inspired for innovation. We want to motivate you to add Reason & OCaml to your professional toolbelt and make you feel comfortable in the ecosystem. This conference is aiming for a well-balanced schedule with a practical, social and theoretical context.
who it's for
Reason developers, frontend engineers using React, tooling and compiler engineers, library and bindings maintainers, engineering managers, open source community maintainers
topics
ReasonReact reducer components; BuckleScript deriving accessors; AST-driven code formatter; editor language server integration; OCaml to WebAssembly C-- backend; GraphQL to Reason codegen; Node.js native addons with camlnode; Belt high-performance data structures; PWA on Kubernetes with Reason; inclusive open source practices
| title | author | length |
|---|---|---|
| Keynote | Cheng Lou | 41m |
Keynote lists concrete wins: the formatter now preserves empty lines; the parser recovers from accidental semicolons so code still compiles; ReasonReact… | ||
| ReasonReact and local state | Cristiano Calcagno | 36m |
A concrete claim: local state via reducer components keeps state minimal per instance so counters stop interfering and only the clicked component re-renders… | ||
| Building inclusive Open Source communities | Laura Gaetano | 32m |
Concrete stats and fixes: the GitHub survey shows 95% men 3% women 1% non‑binary, real harms like Flickr and Google Photos mis‑tagging and a soap dispenser… | ||
| Down the WebAssembly rabbit hole | Sander Spies | 24m |
A concrete path from OCaml/Reason to WebAssembly emerges: the work targets the C-- backend (not the bytecode or lambda only), produces compiled and linked… | ||
| State of the Reason Editor integration | Javier Chávarri | 24m |
Editor integration already delivers hover types, jump to definition, auto completion and reformat driven by Merlin and BuckleScript pipeline and those features… | ||
| Using Reason in traditional Enterprises | Roman Schiefer | 14m |
Claims that Reason yields fewer runtime errors thanks to a strict type system, reports a four-person team building a progressive web app for a large European… | ||
| Reason coming from F# | Lance Harper | 13m |
Shows F# compiling on .NET Core to run on Windows Mac and Linux and using CoreRT to produce standalone binaries, with a concrete workflow to deploy an AWS… | ||
| Practical Interpretation of Code Formatting | Maxim Valcke | 11m |
Claims that the Reason formatter actually rewrites code by modifying the parser and printer and operates on the AST rather than raw text, demonstrates a… | ||
| Having your cake and eating it too — GraphQL in Reason | Sean Grove | 37m |
Argues that marrying GraphQL with Reason eliminates JSON parsing boilerplate and catches API mismatches at compile time by generating Reason types from GraphQL… | ||
| Building native Node.js addons in Reason | Vladimir Kurchatkin | 50m |
Shows how to build a real Node.js native addon from Reason/OCaml: initialize with npm, run camlnode + dune build to produce a .node shared object, and register… | ||
| What’s not to love about Reason? | Keira Hodgkison | 25m |
ReasonReact adoption story with concrete tradeoffs: a team ports a project to ReasonReact and relies on BuckleScript interop for JS snippets, hitting surprises… | ||
| Why We’re Afraid of Change | Jared Forsyth | 24m |
Version numbers lie: a patch like Swift 4.0.1 → 4.2 and a minor like Facebook Android SDK 4.0 → 4.27 both break real apps, forcing a binary search to 4.10.1… | ||
| nothing matches | ||