part of the "unix philosophy"... from the article:
Simplicity
The design must be simple, both in implementation and interface. It is more important for the implementation to be simple than the interface. Simplicity is the most important consideration in a design.
Correctness
The design must be correct in all observable aspects. It is slightly better to be simple than correct.
Consistency The design must not be overly inconsistent. Consistency can be sacrificed for simplicity in some cases, but it is better to drop those parts of the design that deal with less common circumstances than to introduce either complexity or inconsistency in the implementation.
Completeness
The design must cover as many important situations as is practical. All reasonably expected cases should be covered. Completeness can be sacrificed in favor of any other quality. In fact, completeness must be sacrificed whenever implementation simplicity is jeopardized. Consistency can be sacrificed to achieve completeness if simplicity is retained; especially worthless is consistency of interface
an excellent talk about newsqueak, precursor to the go programming language. designer rob pike discusses fundamental concepts that newsqueak (and go) is based on. pike and co have picked up where dijkstra and hoare left off.
pike doesn't analyze this effect explicitly: but the ability to decouple a program's parts into concurrent communicating processes greatly simplifies the management of the program's state space... it's not just new ways to factor code. go has features that support both functional and concurrent construction.
these principles are very important; i expect the combination will trigger a major advance in program design.
i'd also love to see more of backus' work involved, when the time comes :)
i haven't tried this, but it sounds like an impressive accomplishment. From the page: "So by this point you're probably saying, "Yeah right, that's impossible". Show me."
important underpinnings for computer science of the next several decades. i'm not sure exactly how to apply this yet, but we'll be seeing a ton more use for concurrent programming, quickly. the book is a free pdf, and a great read.