Hmm.. concerning security, why not use the good old scheme used from the beginning by UNIX (and event MULTICS before, I guess) ? Allow everybody to write his own NARS2000 workspaces, C programs, possibly shell scripts or even test files, anything, with the following conventions :
1. Only their owner
(logged on NARS2000 forum) can create or modify the original files
2. That creator and owner decides if he/she endorses proposed modifications
stored in some other place.
Let us remember that nothing really bleeding edge is concerned here yet. The idea is just to help other people building their own things without reinventing the wheel every time, especially in uncompatible ways
. I guess that giving NARS2000 some very, very
crude (but possibly very useful as well) graphic possibiities will probably not be a threat to the national security of Western countries. And the West has already contributed so much to helping the world of software that a little, very little more, can probably do no harm.
The idea is that NARS2000 could, from a cleverly written language, become an ecosystem. A host for a contributed workspaces population.
(I even wonder if the IBM folks in Santa Teresa lab would not agree to make some non-commercial arrangement with us
, because every new user of NARS2000 becomes a new potential user of IBM APL2 whenever he/she needs real performance, use of vectorized processing, and the like.
Of course, this could be true of other APL suppliers as well. Just like with drugs, give the first APL for free, and once people get accustomed to it and need to use it in their business, they will complete it by those industrial, expensive - but aimed at performance, not just pedagogy - reasons, I guess).
In 1985, exporting a PC/AT (80286, 1 MB or RAM - not GB ! - and 30 MB of disk to some countries was forbidden by the COCOM. Today, however, nobody would still want to work on such a machine, even a schoolboy. Things are so