Kiko shares the process of building UI components for both client and server sides, highlighting performance benefits and challenges of using server components. Building a reusable UI library with server and client components, aiming for similarity and adaptability. Adding interactivity to a data table in a Next.js application by incorporating client components for reactivity and customization. Building customization by incorporating a custom cell, resolving errors between client and server components, and optimizing syntax highlighting and markdown processing. Achieving composition pattern at the component level by separating client and server parts, maintaining an agnostic component part, and optimizing rendering for client-specific functionalities. Achieving client-server performance optimization by keeping rendering tree agnostic, enabling separate client component extraction, and promoting interactivity within components.

Today's Talk focuses on building enterprise-grade GraphQL APIs with domain-driven design and clean architecture. The speaker shares their experience and emphasizes the importance of understanding the business domain and aligning software with business requirements. They discuss the layered approach of clean architecture and the benefits it provides for separation of concerns and testing. The Talk also covers the use of GraphQL schema merging and mappers to create a unified schema. The speaker concludes by highlighting the importance of constant observation, evaluation, and improvement in software development.

This Talk introduces the use of React and web technologies for building UIs in Minecraft. It discusses the challenges of onboarding new developers to the current tech and the benefits of using open standards. The speaker explains the use of Gameface, a solution for building game UIs with React and Webpack. The Talk also covers state management in a game environment and the use of facets for performance optimization. It concludes with an overview of the Oryui brand and the availability of resources on GitHub.

I'm super excited to be here today, giving my first live talk at an in-person conference. Dominik, the maintainer of React Query, walks through the API design decisions, including success stories, trade-offs, and mistakes. Tener Linsley designed React Query's medium-sized query API to be minimal, intuitive, powerful, and flexible. Major versions in open source require marketing efforts, but not primarily for adding new features. TypeScript is crucial for building projects and managing user demands in open source can be challenging. The addition of the max pages option improved performance and avoided unnecessary refetches. Inversion of control gives users flexibility, but mistakes can happen in API design. Open source requires time management and feedback from users. API design is influenced by typing ease and good TypeScript support. Getting involved in open source involves trial and error and joining community platforms like TanStack Discord. Dominik's journey started during the pandemic and he can be found on Twitter, TanStack Discord, and his blog.

My name is Mauro and I work for a company called Doubleloop in Italy. Today, I'm going to share my learning journey through puzzles and challenges related to React Server Components (RSC). RSC allows for server-side rendering and streaming of components. React flight, a protocol used to serialize and share rendering jobs, is a key feature of RSC. RSC can be used without a server, known as React Serverless Components. Using RSC, different types of content can be switched using the useState hook. RSC can be effectively used on a server by starting Node.js with a specific flag. Client-only components recognized by RSC can be executed on the client. React Streaming Components introduces the streaming concept and allows for continuous updates of the page. Advanced features of React Streaming Components include asynchronous rendering, suspense, and recursion. The React Strange Constraints challenge focuses on optimizing rendering by sending the initial page as HTML. The use of a proxy and RSE payload allows for client hydration of RSC. The possibility of using languages other than JavaScript, such as Rust, for server components is explored. RSC has the potential to become a language-agnostic protocol. The meaning of client-server roles in RSC can be extended. RSC offers streaming capabilities and the ability to balance server and client work. Infinite streaming is possible with server sockets. RSC hydration is believed to be faster than regular hydration. The Talk concludes by encouraging questions during the Q&A session.

In the Talk, various key points were discussed regarding micro-front-end architecture. These included challenges with micro-intents, common mistakes in system design, the differences between micro-intents and components, granularity in software architecture, optimizing micro-front-end architecture, efficient routing and deployment strategies, edge computing strategies, global state and data sharing optimization, managing data context, governance and fitness functions, architectural testing, adaptive growth, value of micro-frontends, repository selection, repo structures, and web component usage.

Sharing insights on scaling AI coding assistance & adopting AI native dev tools. Discussing the need for a shift from viewing adoption as a tech problem to a change management challenge. Exploring a tactical framework with three key phases: onboard, adopt, succeed. Emphasizing the importance of onboarding developers, ensuring access to licenses, and setting clear policies to avoid 'shadow AI'. Highlighting the necessity of human infrastructure for successful AI dev tool implementation, including AI advocates, communities of practice, and executive sponsorship. Adoption strategies require a focus on interconnected metrics and all pillars simultaneously. Leadership checklist for post-conference actions involves measuring metrics, distinguishing between strategic and tactical points, and staying connected through platforms like WhatsApp and LinkedIn.

This talk explores challenges and architecture decisions for realtime apps in React, focusing on frame updates and performance at high refresh rates. It delves into optimizing frame animation, managing synchronization, achieving frame rate independence, and implementing physics in animations. The discussion includes resolving data sharing issues, decoupling data for improved focus, enhancing simulation with external state, customizing animation behaviors, and optimizing continuous updates with Kuta. The talk also covers experimenting with ball physics, tool optimization, and enhancing rendering performance through Canvas, React3Fiber, Sandpack, and Kuta for animations.

Front-end migrations challenges and survival guide. Understanding types of migrations: frameworks, libraries, and infrastructure. Strategies include big bang and gradual approaches, balancing risk, time, and maintenance. Comparing outside-in and inside-out migration approaches. Emphasis on the benefits of the inside-out approach for modernization. Web Components offering a universal way to use components across frameworks. Web Components lifecycle and integration with React. Cross-framework integration of Web Components for smooth migration.