From 515b60cc5ed259db6e93362781e016b9d8124792 Mon Sep 17 00:00:00 2001 From: Brian Vaughn Date: Fri, 1 Mar 2019 08:38:05 -0800 Subject: [PATCH] Fixed a typo in OVERVIEW --- OVERVIEW.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/OVERVIEW.md b/OVERVIEW.md index aa60a29a12..3c1c8eb8bb 100644 --- a/OVERVIEW.md +++ b/OVERVIEW.md @@ -1,12 +1,12 @@ # Overview The React DevTools extension consists of multiple pieces: -* The "frontend" portion is the extension you see (the Elements tree, the Profiler, etc.). -* The "backend" portion is invisible. It runs in the same context as React itself. When React commits changes to e.g. the DOM, the backend is responsible for notifying the frontend by sending a message through the "bridge". +* The **frontend** portion is the extension you see (the Elements tree, the Profiler, etc.). +* The **backend** portion is invisible. It runs in the same context as React itself. When React commits changes to e.g. the DOM, the backend is responsible for notifying the frontend by sending a message through the **bridge** (an abstraction around e.g. `postMessage`). -One of the largest performance bottlenecks of the old React DevTools was the amount of bridge traffic that was sent. Each time React committed an update, the backend sent every fiber that changed across the bridge, resulting in a lot of (JSON) serialization. The primary goal for the DevTools rewrite was to reduce this traffic. Instead of sending everything across the bridge, the backend could only the minimum amount required to render the Elements tree– and the frontend could request more information (e.g. an element's props) on demand, only as needed. +One of the largest performance bottlenecks of the old React DevTools was the amount of bridge traffic. Each time React commits an update, the backend sends every fiber that changed across the bridge, resulting in a lot of (JSON) serialization. The primary goal for the DevTools rewrite was to reduce this traffic. Instead of sending everything across the bridge, **the backend should only send the minimum amount required to render the Elements tree**. The frontend can request more information (e.g. an element's props) on demand, only as needed. -The old DevTools also rendered the entire application tree in the form of a large DOM structure of nested nodes. A secondary goal of the rewrite was to avoid rendering unnecessary nodes by using a windowing library (specifically [bvaughn/react-window](https://github.com/bvaughn/react-window)). +The old DevTools also rendered the entire application tree in the form of a large DOM structure of nested nodes. A secondary goal of the rewrite was to avoid rendering unnecessary nodes by using a windowing library (specifically [react-window](https://github.com/bvaughn/react-window)). ## Serializing the tree