3 ms·
> many kinds of programming could be unified and also be made safer by always using "old" values (from the previous frame) to make new values, which are install
by twic 10y ago
> many kinds of programming could be unified and also be made safer by always using "old" values (from the previous frame) to make new values, which are installed in a the new frame
John Carmack came across this idea at some point - in 'Functional programming in C++' [1], he writes:
"When you start thinking about running, say, all the characters in a game world in parallel, it starts sinking in that the object-oriented approach of updating objects has some deep difficulties in parallel environments. Maybe if all of the object just referenced a read only version of the world state, and we copied over the updated version at the end of the frame… Hey, wait a minute…"
I don't know if he got this explicitly from the Strachey lineage, or if it's the inevitably approach if you try to use immutability to tackle concurrency.
[1] http://www.gamasutra.com/view/news/169296/Indepth_Functional_programming_in_C.php http://www.gamasutra.com/view/news/169296/Indepth_Functional...
- alankay1 10y agoThe way I have looked at this is that a big problem is the confusion of "objects" with "abstract data types" and the clinging to "data" and "assignment statements". As soon as encapsulation is really enforced the object can do what it needs to deal with the design parameters (including keeping histories, etc.). Again: it's really worth looking at Dave Reed's MIT thesis ...
- tankenmate 10y agoThe best way to predict the future is to update^H^H^H^H^H^Hcreate it.