The nomenclature of style: Brutalism, Minimalism, art history and visual style in architecture journals

The naming of styles or movements is a basic mechanism of the architectural journals. The announcement of new tendencies, groups or philosophies, gives a journal its character as ‘news’, and if such terms are taken up in general discourse this demonstrates the prescience of the editor and enhances the repute of the journal. The announcement of phenomenon such as ‘critical regionalism’ or ‘deconstructivism’ referred architectural developments to a context in socio-politics or philosophy, and thus aimed to provide at least an initial resistance to their understanding as the formal styles which they quickly became. A different strategy, or occasion, which this paper will discuss, is where the name of an architectural moment is given in the traditional form of an art historical style. Here the nomenclature of style and a certain attitude to form is introduced as the starting point for a more open ended critical inquiry. Two examples of this strategy will be given. The first is Peter Reyner Banham and the Architecture Review’s promotion of ‘Brutalism’ as an anti-aesthetic which took its conceptual form from early twentieth century art movements, particularly Futurism. The second, identified with Architectural Design in the 1990’s is ‘Minimalism’, a term describing a strand of the visual arts of the 1960’s which can be understood as an attempt to nuance and add seriousness to the present rampant nostalgia for the style of the architecture of the 1960’s.

Obstacles to a totally functional programming style

"Totally functional programming" (TFP) advocates the complete replacement of symbolic representations for data by functions. TFP is motivated by observations from practice in language extensibility and functional programming. Its technical essence extends the role of "fold" functions in structuring functional programs to include methods that make comparisons on elements of data structures. The obstacles that currently prevent the immediate uptake of TFP as a style within functional programming equally indicate future research directions in the areas of theoretical foundations, supporting technical infrastructure, demonstrated practical applicability, and relationship to OOP.