• All you need is the title: Unreal Engine 3 on the 3rd generation iPod Touch. 15 second video, fun to see.
• An extensive post on Bright Side of News about Larrabee should help prime the rumor mill pump for awhile. Quite a lot of info in there (more than I personally care about), lots for Intel-followers to chew on. The bsn* site has much other graphics hardware news.
• The site GLProgramming has infrequent posts on, yes, OpenGL programming. One somewhat surprising document to find there is the OpenGL 1.1 “Red Book”. Admittedly, the hardcopy version is out of print, but only because there is a newer edition.
• There’s a talk on DX11, Warp, and stuff about Windows 7 linked from Microsoft’s DirectX blog.
• So if during your holiday break you want to catch up on the classics (in graphics, of course), see this page. It’s a pretty good list, and there are a few I should read myself.
• The Economist has a pleasant summary of the various display technologies being developed for electronic book devices.
• Speaking of displays, here’s a list of classic computer tropes. Number 26 is “Whenever a character looks at a monitor, the image is so bright that it projects itself onto their face. (See “Alien” or “2001″)”. However, this misses a more interesting point: if the image is projected on a person’s face, the whole image itself is not actually reaching the person’s eye, just a tiny bit of it is.

The Torque game engine is now available for making games on the iPhone. The licensing terms are of the “email us and we’ll tell you” type, but the standard Torque engine is ridiculously affordable for indie game developers at $150, including all source, etc. If you spent all your spare money on an iPhone, oolong is a free engine for games on the iPhone/iPod, originated by Wolfgang Engel and Erwin Coumans, along with assets from PowerVR – it even has a physics engine.

There’s an interesting performance post on cache misses from Dave Moore. Dave Eberly told me a related tale recently: “I am the PS3 programmer.  I spent a lot of time trying to write code to avoid branching, to remove load-hit-stores, and to avoid cache misses. For example, our physics programmer decided that if one function in a class is virtual, then make them all virtual.  He did not realize that a look-up in the virtual function table invariably causes a cache miss.  Make a lot of function calls (like physics systems tend to do), and now you have a serious performance problem.  I removed all the unnecessary virtual modifiers and reduced frame time by 5 milliseconds.  When your goal is 30 fps (33 millisecond frame time), 5 ms is significant.”