As we all know here, size and complexity are two different measures.
On Apr 27, 2010, at 8:08 AM, Bo Jacoby <[email protected]> wrote: I agree that correctness comes first. When a program performs better in some specific cases and worse in other cases then the concept of performance is not well defined. Simplicity is necessary for reliability. Big programs have bugs. --- Den tirs 27/4/10 skrev R.E. Boss <[email protected]>: Fra: R.E. Boss <[email protected]> Emne: Re: [Jprogramming] Polygon containment Til: "'Programming forum'" <[email protected]> Dato: tirsdag 27. april 2010 13.45 Van: [email protected] [mailto:programming- [email protected]] Namens Bo Jacoby Onderwerp: Re: [Jprogramming] Polygon containment I think that one should usually resist the temptation to introduce additional complexity into a program in order to speed it up a little in special cases, because it may turn out to be slower in some other cases, which is bad, and simplicity is lost, which is worse, and also bugs may be introduced, which is very bad. (...) My priorities differ: correctness comes first, then performance, then elegance. Efficiency improvements only count from a factor 2 upwards (Hui's rule). So "to speed it up a little in special cases" is too dismissive. R.E. Boss ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
