News for hackers. Stuff that matters.
Re:CSS-Powered 3D Engine (2014) by contrahax on Sunday February 24, 2019 @01:42PM (#19239876)
Secret sauce was basically every element absolute positioned, with an event loop that was diffing a CSS transform tree each tick. Worked pretty well, but was basically a workaround for browser performance issues that ended up being fixed anyways. (Was hired by them to do their React component library long ago)
Re:CSS-Powered 3D Engine (2014) by pavlov on Sunday February 24, 2019 @06:47PM (#19241448)
It’s an awfully big stretch to hype that up as some kind of direct GPU access, as in this quote from the TechCrunch article about the pivot:

“By bypassing the CSS and HTML renderers to talk directly to the graphics processing unit, Famo.us could supposedly make 3D physics and other visual wizardry common with native games run smoothly for apps in a mobile or web browser.”

Re:CSS-Powered 3D Engine (2014) by underwater on Sunday February 24, 2019 @09:45PM (#19242400)
Journalists always simplify things to the point they become meaningless.

But avoiding DOM layout and its performance issues was relatively innovative at the time. It wasn't unheard of, but no one had really turned it into a framework like they did.

Re:CSS-Powered 3D Engine (2014) by pavlov on Monday February 25, 2019 @05:06AM (#19244464)
You can't blame journalists when the CEO of the company was actively spouting this "interfaces directly with the GPU" bullshit to describe multiplying some matrices in JS.