[no subject]

As we've discussed at length over the years, parallel programming
really is the new frontier in software development, and the vast
majority of the programming fraternity remains hopelessly unable to
exploit the potential power. This includes, unfortunately, current
consumer class machines that contain 2-8 processing units with shared
fast memory! Having the technology available to begin to experiment
has resulted in very little software in the wild having anything more
than 'token' support multiple procesors (embarrassingly parallel
problems excluded), so the adoption issues you're suffering from
certainly aren't unique to NadaNet.

Since sequential programming already demands so much of our spatial
reasoning, I guess it shouldn't come as a surprise that there's so
little left over to consider time as a two dimensional quantity. My
own experience with parallel application development over the years
has taught me that even the most innocuous looking construct, say
using a mutex to serialise access to a resource (the proverbial
critical section) is fraught with hidden complexity.

Given that, I think it would probably beneficial to provide a small
collection of contrived examples. How do we implement serialised
access to a resource? What about many readers but only one writer? A
NadaNet equivalent of the Dining Philosophers, etc.

Anyway, enough of that and onward to more positive things and perhaps
a discussion point: What could be done with 1 (or perhaps 2) slave
machines attached to a developers primary Apple II? This is a
configuration I think most of us could scare up easily and since we're
talking developers how about ...

An interactive, incremental,  Editor/Assembler/Debugger ?

Matt