Clientside: From WASM to Browser Applications

From Mixins to Custom Hooks: History of Sharing in React

React’s component-driven design simplifies reusing UI because chunks of markup can be encapsulated into custom components. Likewise, sharing traditional data utilities is straightforward because React is “Just JavaScript”™. But what about sharing non-visual component logic like state shape and lifecycle methods? React has had several approaches over its lifetime to solve this problem: mixins, higher-order components (HOCs), render props, and now hooks, each with their pros and cons.

In this session geared towards current React developers, let’s take a history lesson on sharing in React in order to better understand how modern-day custom hooks work and the problems they solve. By the end, not only will we know how hooks function, but we’ll also be equipped to pull out non-visual component logic into easily shareable custom hooks in our apps.

Create Autonomous, Highly Productive Teams By Lowering the Stakes

Every company's dream is to have highly productive teams that ship quickly and reliably, self-start while supporting the company's overall strategy and goals, and create as little maintenance overhead and technical debt as possible. Unfortunately, this dream is often undercut by slow internal processes, unclear ownership, and organizational roadblocks (both unintentional and otherwise).

In this talk, we'll look at architectural and organizational strategies to help free teams up to move more quickly without increasing technical debt or maintenance burdens. We'll identify several common pitfalls that slow teams to a crawl and sap motivation, as well as small adjustments that will help you avoid them. By the end of this session, you'll have clear action items that will allow your company to unlock the potential or your teams and rekindle their motivation to build incredible things!

Server-Side Wasm: Today and Tomorrow

Wasm has already started making waves in the web development community, enabling developers to run code written in various languages at near-native performance. There is so much potential for Wasm to enable similar capabilities outside of the browser, which is what I explore in this talk. Docker made it easy to run full-blown server applications in a portable way, but Wasm has the potential to take this even further; by enabling developers to write individual serverless functions in the language of their choice, and load them as hot-swappable modules.

I explore Wasm as it is today, and the capabilities that Wasm will bring us tomorrow. I'll use the Suborbital Development Platform to illustrate how Wasm modules can be used to compose powerful server APIs, and talk about what the future of extra-browser Wasm might look like. I discuss how Wasm will enable highly modular code, increased security and performance, and how it intersects with Docker and the Serverless ecosystem.

Clientside Panel

The Speaker is preparing the presentation abstract. More details will be available soon.