Just one little thing

Murphy's Law fate@ccwf.cc.utexas.edu
Sun, 7 Mar 93 07:19:06 -0600


(Excuse me if this doesn't get out, or gets Fubared along the way..)
 
On a different vein from what we have been discussing, but one that should
be considered is the format / use of executionable code.  While having
objects for them is just about a given, it remains the task of the 
kernel to load and execute programs, otherwise, the o/s will be about worthless
without "applications" 
 
So, a suggestion would be to implentate, FORCED public/private key authorization
of any application that would have a priority level over the lowest one.
While allowing for applications to be debugged / developed, but not allowing
viruses/worms/ other friendly things that chew away on your data.
 
As far as graphical/text interface goes, this seems that it should be 
related to the concept of a shell.. either a cmmmand.com equivalent, or a
"finder" equivalent.  to use examples from O/Ss that I suffer with.  This
would load a library into memory that would handle display calls.  If 
some features of the display library are necessary, ie, graphics, and the user
is running in text mode, there could be a loader program that would load up the 
library for graphics and remove it when no longered needed..  And those with
fast machines, or masochists, could enjoy the slow updating of a pixel base
interface.