Interview with Dan Abramov on React Server Components, Vue Comparison, and Frontend Architecture

On July 5, 2021 the ByteDance Web Infra team and the ByteDance Technical Platform Front‑end team hosted a technical interview with Dan Abramov, a core developer of the React team, covering many React topics that interest Chinese developers.

Dan explains that Server Components are an experimental feature released as a preview in December 2020. They run only on the server, are not downloaded to the client, and act like an API that can directly access databases or micro‑services, reducing client‑side code and improving performance. Using a framework such as Next.js you can enable Server Components simply by naming a file .server.js .

When asked about the perceived complexity of maintaining three component types, Dan clarifies that developers still write only Client Components unless they need Server‑side capabilities; the three categories (Server, Client, Shared) are just additional options, not mandatory extra work.

Regarding the comparison between React and Vue, Dan notes that Vue is built on mutability while React pursues immutability, leading to different design philosophies and trade‑offs. He emphasizes React’s focus on reliable, well‑tested solutions rather than quick compromises.

On the use of Flow versus TypeScript, Dan says Flow remains in the React codebase for historical reasons, but the choice does not affect React users and could be switched to TypeScript at a high migration cost.

When discussing newer frameworks such as Svelte and Solid‑js that claim to drop the Virtual‑DOM, Dan argues that the Virtual‑DOM is a conceptual in‑memory representation that enables features like Server Components and animation interpolation; it is not a direct performance metric.

He outlines various rendering models—SSR, CSR, NSR, ESR—and recommends using frameworks like Next.js (or Shopify’s Hydrogen ) to abstract the complexity of choosing where code runs.

Dan describes React as a library rather than a framework, but one that is evolving into an architecture with opinions on data‑fetching, routing, and server‑side rendering, allowing different frameworks to build on top of it.

He shares what attracts top front‑end talent: a learning‑rich environment, mentorship from senior engineers, and high autonomy in choosing tasks.

For learning the React codebase, Dan suggests reading open issues, using debuggers, and analyzing Chrome Performance flame graphs to understand hot paths and core functions.

Maintaining React’s massive repository relies heavily on extensive automated tests—especially public‑API tests—to ensure refactors do not break behavior, and on a dual‑file versioning strategy (.old.js/.new.js) for safe experimentation.

Dan advises that reading the entire source is optional; instead, stepping through code with a debugger or performance tools provides practical insight.

He stays passionate about React because its declarative UI model aligns with his programming mindset, and he looks forward to simplifying data‑fetching, animation, and code‑splitting in future releases.

For learning resources, Dan recommends building small, deep projects (e.g., a custom autocomplete or a simple game) without relying on libraries, to strengthen fundamental skills.

Outside of work, Dan enjoys listening to music, walking, and occasional gaming like Fortnite.

He mentions his side project justjavascript.com , a free‑for‑now JavaScript course that will soon become a paid offering, focusing on visual explanations and hands‑on implementations.

Finally, Dan expresses gratitude to the Chinese React community, encourages more translation and local events, and looks forward to further collaboration.