Remember, the bare hardware without any software at all has the greatest potential. Every line of code added to the software system takes away from that potential. This is necessary, of course. You have the hardware for specific purposes, and the software serves these. But one should not ignore the cost in lost capability.
Let's assume you got an operating system, that let's an application take total control of the hardware, like DOS did. Clearly the OS provides a service by loading the application. Then the application overwrites the OS with data, so as to not waste any space before it delivers the result and after producing the output it terminates by going into an undefined state, so as not to waste any space for termination code.
So how does this OS limit the hardware? - sure it limits the program length available for the application,
but in practice this opposed, orthogonal, features, capabilities is all ... How do you define a capability of a program with 0 (zero) features? _______________________________________________ geda-user mailing list geda-user@xxxxxxxxxxxxxx http://www.seul.org/cgi-bin/mailman/listinfo/geda-user