Virtual DOM is pure overhead (2018)
I&#x27;ve heard the term &quot;virtual dom&quot; for years. This article made me want to understand. It gives this example for explaining &quot;what is a virtual dom?&quot;<p><pre><code>  function HelloMessage(props) {
    return (
      &lt;div className=&quot;greeting&quot;&gt;
        Hello {props.name}
      &lt;&#x2F;div&gt;
    );
  }
</code></pre>
And that returns &quot;an object representing how the page should now look&quot;<p>Aren&#x27;t we developers here. How about an object type. 
I assume it&#x27;s a DocumentFragment. Is that correct?<p>Then it talks in broad (i.e. useless) terms about using this object.<p>So my next question is: what&#x27;s exactly is wrong with using a DocumentFragment to just replace that part of the DOM? For example:<p><pre><code>   let frag = renderMyModel();

   if (destElt.firstElementChild) {
      destElt.replaceChild (frag, destElt.firstElementChild);
   } else {
      destElt.appendChild (frag);
   }
</code></pre>
I do this with a massive DOM tree and rendering is like instant.