> The browser is a GPU-backed renderer. That matters very little. By that logic, everything is GPU backed these days and rendered by a compositor, on all platf

> The browser is a GPU-backed renderer. That matters very little. By that logic, everything is GPU backed these days and rendered by a compositor, on all platforms. > At some point with your own renderer you have to implement a large part of the DOM No, not really. Unless you are saying "DOM" to mean any tree structure. And you might not even need that for your app, depending on its layout. When people say "GPU rendering" in this context, think user interfaces found in games. They are directly rendered by the game code without any intermediate layers. And very often, without anything that one would even remotely recognize as a DOM (3D games have a scene graph, but that's still different). > And why should a text editor team have to do that? Ask Sublime Text and iTerm. They already do that to render their content (and implement native OS dialog controls for the rest). > I think a lot of teams would be better off by learning how to make faster web apps True, just because of the amount of effort. _Users_, on the other hand...