The DOM already does dirty-checking on manipulation.  Manipulating the DOM is cheap, it&#x27;s manipulating the DOM <i>while also getting dimension or style information</i> that&#x27;s expensive.<p>None of the major frameworks solve this problem.  The closest may be React, which strongly discourages you from interacting with real DOM nodes or doing anything stateful, but even then, if you really want to touch that offsetWidth you can trivially destroy React&#x27;s performance.  Maybe the best alternative is just strict coding standards that say &quot;Don&#x27;t do that!&quot;<p>I&#x27;d talked with a few Chrome PMs when I was working on Material Design for Google Search and discussed the possibility of some sort of batching API for layout-causing operations.  They weren&#x27;t against it in principle, but nobody could think of an API that was something we&#x27;d actually use as web developers.  The problem is that thinking about your app in terms of &quot;This expression causes layout, this expression dirties the DOM&quot; is a big cognitive load, and making those two classes of expressions non-interleavable means you suddenly need to structure your whole app in different ways.<p>There&#x27;d also been talk of doing a subset of HTML that includes only the operations that can be done quickly, but to my knowledge, that never went anywhere.  You run into problems with the whole huge installed base of the web; if you&#x27;re going to throw everything out and start from scratch, why not just use a native mobile app, or even raw OpenGL ES commands?