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
Tilted Arc An Artwork by Richard Serra www.artdex.com In the 1980s, Serra found himself in the center of a public controversy over his piece titled Tilted Arc. While it was the government that approached him to create the work for downtown Manhattan’s Federal Plaza, the unveiling of the piece in 1981 was met with sharp criticism. The monumental sculpture was said to disrupt rush hour and the pedestrians who had to cut through the plaza daily. To the dismay of art lovers, the 120-foot-long, 12-foot-tall Tilted Arc was ultimately disassembled in 1989. Weathering SteelWrapped Reichstag20 Minutes in ManhattanPortal Park Slice cities