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
1º2º3º4º Because the approach to the room is along a long corridor, the attentive visitor might at first think that three light squares had been affixed to the windows or, as one gradually came closer, that the tinting of the windows had simply been removed in these three lighter near-square areas. Davies continues: "only at this point do the other senses kick in. The visitor begins first to hear and smell the ocean and then to actually feel the outside air entering the gallery; this sensory experience is in complete contradiction to the faulty first impression." Robert Irwin, Robert Irwin: A Conditional Art The inhumanity of contemporary architecture senseswindows