This is an amazing insight into how demos are written. Farbrausch stuff has always been inspirational to me.

It's very interesting is the sort of extreme version of the idea that data model and code are inherently tied: Especially in functional programming circles it's a maxim that you design your data models first, specifically for your task, and then the rest of the code is pretty much pattern-matching around that. This takes that coupling and makes it even tighter, to serve a higher purpose. I almost feel like given enough time, this could be a JIT: an executable that adaptively strips code and self-minifies over time as you run it. :)

Also check out:\n- kkrieger (windows only 96kb 3D FPS, video here: https://www.youtube.com/watch?v=2NBG-sKFaB0)\n- the previous post (http://fgiesen.wordpress.com/2012/02/13/debris-opening-the-b...)

For the curious, Farbrausch have a released a lot of their demos and tools source code on GitHub: https://github.com/farbrausch/fr_public

(Also, take a look at the rest of Fabian's blog, it's extremely good.)