Looks like a nice 3D tweening DOM engine. Related (and recommended) visits for people interested in that sort of thing: - http://hakim.se/ http://hakim.se/ -

Looks like a nice 3D tweening DOM engine. Related (and recommended) visits for people interested in that sort of thing: - http://hakim.se/ http://hakim.se/ - http://desandro.github.io/3dtransforms/ http://desandro.github.io/3dtransforms/ - http://glmatrix.net/ http://glmatrix.net/ As for the article... the author confuses "rendering" with "layout": - "the primary part we need to rewrite is the part of the renderer that creates and multiplies the matrices" - "We use the CSS3 primitive -webkit-transform: matrix3d, which lets us compute the composite matrix and skip the browser's renderer" Which leads to some absurd claims: - "We were 14 times faster than compiled C in Chrome" Before reality kicks back in: - "rendering goes through DOM" - "Obviously, this isn't exactly the reinvention of the Web" And this is how you sell a DOM scenegraph engine to people with more money than common sense: - "a W3C standard that must be supported by all browsers" - "all text in Famo.us applications is searchable" - "enable rapid application development" - "smooth, high-functioning UI across all platforms" - "one of several enabling technologies" - "allow enterprise users to touch-interact with big data analytics" - "spark a new breed of gamified enterprise apps"