Talk:Greenspun's tenth rule
| WikiProject Computing / Software | (Rated Start-class, Low-importance) | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||
| WikiProject Systems | (Rated Start-class, Mid-importance) | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||
Archives (Index) |
|
This page is archived by ClueBot III.
|
Talk[edit]
Same thought found June 1970 Forth material copy-restricted till like 2011[edit]
A much earlier source of nearly the same aphorism is: """ any application of sufficient complexity, and surely any application of any generality, much develop a specialized language """ pp.55-56 of 142 http://www.forth.org/POL.pdf https://en.wikipedia.org/wiki/Charles_H._Moore June 1970
There it is fleshed out like so: """ You started with a program that controlled an application. You now have a program, that provides the capability to control an application. In effect, you have moved up a level from language to meta-language. This is an extremely important step. It may not be productive. """
And again: """ ... leads you from talking to your application to talking about your application ... You change from an application [programmer] to a system programmer - your system being your application """
- Start-Class Computing articles
- Low-importance Computing articles
- Start-Class software articles
- Mid-importance software articles
- All Software articles
- Start-Class software articles of Low-importance
- All Computing articles
- Start-Class Systems articles
- Mid-importance Systems articles
- Systems articles in systems engineering
- WikiProject Systems articles