Complete your registration early to skip the line at the venue! Look for the tables in the hotel lobby. Be sure to have your Tito ticket QR code at the ready! Connect with your fellow attendees on Slack (or in the lobby) for breakfast and lunch!

On-site registration. Beverages and light food service offered

From components to JSX to hooks, React has been a beacon of innovation for the web dev world. It didn’t start that way though. When we first saw React’s abstractions in 2012, we were horrified. We eventually were convinced. Now, the roles have reversed. Gatsby, Next and Remix all showed the need for React on the server. It took a bit, but the React team caught on. For the last decade, the community has adopted React’s innovative patterns. This time is different. The innovation of Server Components didn’t come from React. It came from us. In this talk, I’ll be discussing our responsibilities as the new shepherds of React, the React community itself.

After a decade of REST APIs, developer tools have evolved to speak a new language: React Components. From Next.js's <Image/> to Clerk's <SignIn/>, components have rewritten the rulebook for how much power can be packed into a single line of code. They bundle a frontend with an API, and offer a ridiculously fast, 'lego block' integration experience. But what makes a good component? There is no REST convention to follow, and publishers have landed on dramatically fragmented solutions to challenges like styling, routing, and composability. In this talk, we'll explore the rise of components as the ideal developer tool, and unpack the tradeoffs among these fragmented approaches.

Many React developers use server rendering to improve performance. Before React 18, however, all four (4) steps in the server rendering process (data fetching, rendering to HTML, loading JavaScript, and hydrating) had to be completed for the entire app at once. This meant that a bigger or more complex part of your app would block other parts from moving onto the next step, making your app appear slower. Thanks to optimizations in React 18, you can use Suspense to break your app into smaller parts that go through these steps independently. Users benefit from an app that they can see sooner and interact with almost instantaneously!

Discuss the first session's topics with your fellow attendees, speakers, and visit the sponsor booths! Additional food service & beverages provided.

React server components (RSC) were initially announced in 2020 and finally made broadly available as a beta via next.js a few months ago. There has been talk and hype around them for years, but genuine understanding of what they are, how they work, and where they shine vs struggle is in short supply. In this talk from the former engineering manager of the next.js team, we'll go into depth on RSC from a balanced perspective, and together we will build a solid understanding of when RSC is the right tool to solve the problems you're facing, and when to look elsewhere. We'll also work through practical examples of RSC in action, and take steps towards shifting your perspective into understanding the new architecture model that RSC sits on top of.

This panel will explore the community-driven solutions on server components. Shruti Kapoor will sit down with Tanner Linsley from the Tanstack, Fred Schott from Astro, and Ryan Carniato from Solid.js to discuss their approaches to server components. Topics covered may include: When & how do these library maintainers integrate, or recommend, server-side rendering in their architectural framing? How does it differ from the React core team's approach, and what does that tell us? What is their long-term vision and/or plan for server components? Footguns, latest innovations, lessons learned from the past and from each other, etc.

Come chat with speakers, open source maintainers & core contributors, and other attendees at the topic tables! Loosen up with a drink or stay sharp and sober as you mingle with speakers, sponsors, & fellow attendees!