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
Irwin Volumes Show image 0 Show image 1 Show image 2 Show image 3 Show image 4 Black Line Volume, String Line-Light Volume, Corridor String Piece, Line Rectangle "The resultant black rectangle was not what you "looked at" – there was actually nothing to focus on – but soon it brought the space into focus with a distinct visual snap. From inside, the light in the area seemed different, more substantial, and the wall color began to shift ambiguously. From outside the area, the tape seemed to lift the plane of the floor upward in your field of vision, and it also made the room seem wider and shallower than it really was." — Roberta Smith Robert Irwin, Robert Irwin: A Conditional Art You are the one that is changed