Partial hydration, also known as the Islands architecture, allows for only certain parts of a page to be hydrated, improving performance by reducing the amount of code sent to the browser.

By switching to Islands for interactive components, you can achieve a 75% reduction in the size of the application, which can lead to a fourfold improvement in loading time.

In server-side rendered applications, the time to interactive is proportional to the amount of content on the page, meaning more content can slow down loading and interactivity.

WebAssembly currently cannot directly call browser APIs due to its sandboxed nature, requiring data to be passed through JavaScript, which can introduce latency.

WebAssembly and JavaScript have different costs in the browser; JavaScript is interpreted and must be fully downloaded and parsed, while WebAssembly is designed for streaming compilation, making it faster to load.

JavaScript frameworks require a large amount of code to be shipped, which can cost companies millions in loading time, making them less appealing for e-commerce applications.

With the recent release of code execution for HTML and React, I can preview visualizations and interact with them directly.

Our architectural choices, such as multi-query attention, enabled us to control speed and latency more precisely without hurting user engagement.

Before writing a line of code for Next.js, I outlined seven principles of what the ideal state-of-the-art web would be, including instant loading and real-time data.