Sean Grove

2019

ReactiveConf

Lightning Talk

Sean gives an amazing overview of Rust, for JS developers.

Thanks to wasm, Rust can reach the platform with the largest reach: the browser. We’ll take a look at how thanks to the impressive language design, thoughtful compiler error messages, and great documentation, JavaScripters can unlock high-performance concurrency and graphics thanks to Rust. 

We’ll step through Rust/wasm/JS interop, see what it’s like to get a reference to a canvas instance, to communicate with services workers, and to pass data between all the pieces involved. We’ll take a look at what’s enabled, as well as pitfalls around the data boundaries involved, and the size of the final payload, so that it’s clear where the cost of introducing Rust is outweighed by its benefits. 

Finally, we’ll speculate on how the web may develop, with a Rust-core/JavaScript-surface design, combining high performance, safety, while maintaining ease-of-use.

Rust in the Browser for Javascripters: New Frontiers, New Possibilities

Every JAMstack app at its core does 2 things for users:
- Reads data from sources (DB, Stripe, Salesforce, Shopify, etc.)
- Effects the world on their behalf (sending emails, submitting purchases, etc.)

Yet combining APIs into a coherent unit is intensely manual & fiddly.
Instead, let's combine multiple persisted queries in GraphQL to succinctly encompass all of the chaining work.

We'll build one such sequence to expose as a single call for our JAMstack app that:
- Takes a domain-name input from a user
- Purchases the domain
- Creates a GitHub project
- Deploys a placeholder on Netlify

2019 San Francisco

JAMstack Conf

Supercharging JAMstack apps with multiple APIs via GraphQL Pipelines

Traditionally, soundly typed-language are warm and cozy in their own world, but as soon as they have to deal with the outside world (say, talking to a REST API), the pain quickly sets in: trying to keep a type definition in sync with a moving external service, manual conversion back and forth, and lots of boilerplate.

Well no more!

Proper GraphQL support in ReasonML libraries means that we can have full-stack safety, knowing that if our programs compile, the server can satisfy our requirements! And on top of that, we get all the other GraphQL goodies, like tooling, in-editor auto-complete, and fantastic compile-time optimizations, for free!

But what about the server-side, you ask? There are so many places things can go wrong when trying to maintain the promises you give to your GraphQL clients, I hear you cry out!

Dry your eyes, friend, for `ocaml-graphql-server` is here to guide you to the happy full-stack GraphQL+Reason world you’ve been dreaming of, where whole classes of errors are eliminated.

As in any good talk, however, we’ll also take a look at some of the painful points of this approach, and how ReasonML might make some tasks more difficult so that you can leave with a confident understanding of whether this new frontier is one you want to brave any time soon.

2019 Lithuania

You Gotta Love Frontend

Having Your Cake and Eating It Too GraphQL in Reason

2018

Help Your Computer Help You

2017

Lightning Talk - Sean Grove

Reason is a new developer experience by Facebook built and championed by the same people behind React. Based on OCaml, it offers powerful type-checking, incredible tooling, fantastic performance, and truly unbelievable reach (as in you'll be sceptical that it's possibly true).

Let's look at the range of practical capabilities of Reason - building universal apps that output browser-targeted code indistinguishable from hand-written Javascript but also compiles down to ARM64 assembly for native iOS apps, or replaces 15 *million* lines of memory and type unsafe operating-system code to create unikernel servers that boot in 50 milliseconds and weigh between 200KB-10MB, all from the same codebase - to the more philosophical, such as how Reason is the first language ever to separate syntax and semantics, and all of the resulting implications - and even the more whimsical, like Reason's relentless focus on developer simplicity and joy.

Full-stack apps in one language, from hypervisor unikernel to clients written in React (or ReactNative) - As easy as JavaScript, as delightful as Elm, as powerful as native, and with unprecedented reach - we're finally entering into an age of Reason.

2016

The Age of Reason(ML)

Dato is a new way of building applications, heavily inspired by Meteor/Firebase/Relay, but informed by functional, data-oriented programming techniques. 
The goal is to provide:
Seamless, permission-aware data synching between the sever and n-clients
Seamless, permission-aware rpc invocations
A more flexible, intuitive UI layer
Advanced tooling layer for time-traveling debuggers, state serialization, component layout, query editing, performance optimizations, and others.
Integration on the backend to stream into analytics, session replay, 3rd-party integration