Recognizing Constraints An Article by Jeremy Wagner css-tricks.com Super Nintendo games were the flavor of the decade when I was younger, and there’s no better example of building incredible things within comparably meager constraints. Developers on SNES titles were limited to, among other things: 16-bit color. 8 channel stereo output. Cartridges with storage capacities measured in megabits, not megabytes. Limited 3D rendering capabilities on select titles which embedded a special chip in the cartridge. Despite these constraints, game developers cranked out incredible and memorable titles that will endure beyond our lifetimes. Yet, the constraints SNES developers faced were static. You had a single platform with a single set of capabilities. If you could stay within those capabilities and maximize their potential, your game could be played—and adored—by anyone with an SNES console. PC games, on the other hand, had to be developed within a more flexible set of constraints. I remember one of my first PC games had its range of system requirements displayed on the side of the box: Have at least a 386 processor—but Pentium is preferred. Ad Lib or PC speaker supported—but Sound Blaster is best. Show up to the party with at least 4 megabytes of RAM—but more is better. constraints
What the painting was not about That is why for many years Irwin declined to allow his work to be photographed, because the image of the canvas was precisely what the painting was not about. Indeed, the problem is even more complicated than that. For in a very real sense the achievement of these paintings was in their making, and the finished canvas at one level is only an incidental relic, a fossil of that original process of discovery: not only do you have to be present before these paintings in order to experience them, it may be that you have to have made them as well. Lawrence Wechler & Robert Irwin, Seeing Is Forgetting the Name of the Thing One Sees Only a mind opened to the quality of things photographyimages