From de2c2850fcfd01d00819df62959edad9b09edd9e Mon Sep 17 00:00:00 2001 From: Sunreal Date: Thu, 26 Nov 2020 23:36:40 +0800 Subject: [PATCH] Update optimizations.md --- src/guide/optimizations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guide/optimizations.md b/src/guide/optimizations.md index be3352dff7..46303af8c5 100644 --- a/src/guide/optimizations.md +++ b/src/guide/optimizations.md @@ -12,6 +12,6 @@ Now that we know how watchers are updating the components, you might ask how tho We make a copy of the DOM in JavaScript called the Virtual DOM, we do this because touching the DOM with JavaScript is computationally expensive. While performing updates in JavaScript is cheap, finding the required DOM nodes and updating them with JS is expensive. So we batch calls, and change the DOM all at once. -The Virtual DOM in is a lightweight JavaScript object, created by a render function. It takes three arguments: the element, an object with data, props, attrs and more, and an array. The array is where we pass in the children, which have all these arguments too, and then they can have children and so on, until we build a full tree of elements. +The Virtual DOM is a lightweight JavaScript object, created by a render function. It takes three arguments: the element, an object with data, props, attrs and more, and an array. The array is where we pass in the children, which have all these arguments too, and then they can have children and so on, until we build a full tree of elements. If we need to update the list items, we do so in JavaScript, using the reactivity we mentioned earlier. We then make all the changes to the JavaScript copy, the virtual DOM, and perform a diff between this and the actual DOM. Only then do we make our updates to just what has changed. The Virtual DOM allows us to make performant updates to our UIs!