Topic: domain specific language
Topic: general purpose computer systems
Topic: handling complexity
Topic: identifying program modules
Topic: minimal language systems
Topic: orthogonal extension and cartesian products
Topic: specific purpose computer systems
| |
Subtopic: generalize only as necessary
Quote: generalize a system only as necessary; it should have a medium level of generality [»akscRM5_1984]
| Quote: an interface should capture the minimum essentials of an abstraction, without generalization [»lampBW10_1983]
| Quote: consensus design encouraged too many requirements and generalized designs [»corbFJ_1979]
| Quote: in Multics an elaborate macroassembler failed; replaced by a simple, primitive assembler [»corbFJ_1979]
| Quote: a general-purpose system can not optimize the use of resources; too easy to overload the system and degrade service by thrashing [»lampBW10_1983]
| Quote: often better to use a straightforward, brute force solution that is easily analyzed, than a poorly understood one [»lampBW10_1983]
| Quote: if in doubt, split resources instead of sharing them; faster allocation and access, more predictable [»lampBW10_1983]
| Quote: a functional design leads to a virtually unlimited wish list of features [»joneTC4_1979b]
| Subtopic: systems depend on domain
Quote: producing valid systems is a domain dependent activity [»blumBI8_1985]
| Subtopic: many specific vs. few general
Quote: many programming constructs, may be better than one or two general-purpose constructions [»greeTR_1980]
| Subtopic: model vs. application
QuoteRef: seedH_1971 ;; [cbb: RPG very good for simple problems by gets very complicated very fast
|
Related Topics
Topic: domain specific language (8 items)
Topic: general purpose computer systems (9 items)
Topic: handling complexity (60 items)
Topic: identifying program modules (26 items)
Topic: minimal language systems (12 items)
Topic: orthogonal extension and cartesian products (11 items)
Topic: specific purpose computer systems (9 items)
|