Great idea. Spend 10 minutes writing your framework that gets you 80% of the way. Can&#x27;t wait for the next decade worth of follow-ups that attempt to patch up the remaining 20%.<p>Frameworks don&#x27;t exist just because someone wanted to write a framework. They exist because they solve problems. And they solve problems you likely forgot to think about so you don&#x27;t have to. Like not losing cursor positions when re-rendering, or not breaking the DOM when trying to re-use input elements or manipulate tables.<p>React is actually great in this regard: it doesn&#x27;t try to solve everything, it just focusses on one problem (two if you include React-DOM&#x2F;Native) and solves it well. Redux is another great example (the entire API can be implemented in less than 100 lines).<p>The reason libraries and frameworks like React and Backbone and Angular and Ember exist is that direct DOM manipulation doesn&#x27;t scale. It&#x27;s on a lower level of abstraction than the application you&#x27;re trying to build. And the advantage of React (and similar libraries like Mercury) is that it just lets you build components (i.e. partial DOM trees) -- it&#x27;s trivial to swap the component library out in the future without having to touch any of the application logic around it.