Negroponte, in the YouTube posted today, keeps using the word “Orthogonal”. I’m not sure if I’ve ever heard it before in my life, and I definitely didn’t know what it means. Since he used it a lot, seems like we should know what it means.
Here’s a definition I found online, but I’m not sure if it fully encompasses, or reflects exactly what Nicholas was using it to say, because as I admitted, I’m lacking past context of meaning for this word.
In geometry, orthogonal means “involving right angles” (from Greek ortho, meaning right, and gon meaning angled). The term has been extended to general use, meaning the characteristic of being independent (relative to something else). It also can mean: non-redundant, non-overlapping, or irrelevant. In computer terminology, something – such as a programming language or a data object – is orthogonal if it can be used without consideration as to how its use will affect something else.
In itself, a programming language is orthogonal if its features can be used without thinking about how that usage will affect other features. Pascal is sometimes considered to be an orthogonal language, while C++ is considered to be a non-orthogonal language.
Features of a program that is compatible with its own earlier versions – this is calledbackward compatible – have an orthogonal relationship with the features of the earlier version, because they are mutually independent; you don’t have to worry about how the use of one version’s features will cause an unintended effect because of an interaction with those of the other version. Both the features and the programs can be said to be mutually orthogonal.
The length of time data is kept in storage in a computer system is known as its persistence.Orthogonal persistence is the quality of a programming system that allows a programmer to treat data similarly without regard to the length of time the data is kept in storage. Data is stored for varying lengths of time; some is stored very briefly and some is stored relatively permanently. Frequently, a programmer must use different approaches and separate coding to access data depending on whether it is stored for a long time or a short time.
Using a programming system with orthogonal data persistence allows the programmer to treat data the same way regardless of its persistence characteristic, saving programming time and making it easier to enforce referential integrity (a type of constraint applied to ensure correct data validity).