hmm, what exactly does he mean by data-oriented programming?

iirc that's something where you don't store data chopped up into objects, but have arrays that keep all the data of one "aspect" of all "objects"... or something like that. something game programmers would use, helps avoid cache misses.

is that what he was talking about? if so, what does it have to do with macros?