I'm so happy that this comment is here and the top most voted comment. I keep making this point every time web apps come up. I still don't understand why the us

I'm so happy that this comment is here and the top most voted comment. I keep making this point every time web apps come up. I still don't understand why the user agents still haven't started work on a retain-mode scene graph for the web that plays nicely with HTML when a document is needed. I really want a graphics system in the browser that can do the types of things being done here: https://news.ycombinator.com/item?id=7896773 https://news.ycombinator.com/item?id=7896773 i.e. Wayland for the Web with documents If we jump on this now, maybe we won't be left in the dust when native makes the jump from 2D to 3D and interface devices like the Oculus Rift go mainstream. This is probably 5+ years away, but now is the time to start considering how these capabilities will be possible at the lowest levels. None of this precludes the entire 2D web we're familiar with since 2D is simply an elevation view of 3D. Baking 3D in from the start leaves room for people to explore the possibilities people are exploring on native instead of being hamstrung by naïve technological choices. We're trying to explore what is possible here at famo.us [0]. Hopefully between what we're doing and what others are exploring, we'll come up with some interesting approaches that eventually made their way somehow to becoming a standard. The w3c spends too much time trying to expose APIs for the jQuery level developers instead of seeing the web as an operating system and exposing operating system primitives from day one. All they need to do differently from how previous operating systems worked is consider how the semantic web, accessibility, and URIs fit into this computing model. relevant: http://acko.net/blog/shadow-dom/ http://acko.net/blog/shadow-dom/ [0] http://famo.us/ http://famo.us/