Originally posted by jackd
the programmer can make apps use multiple processors more effectively by "threading" them-- that is, spinning off separate threads of execution.
I totally agree, but this good programming practice has nothing to do with the number of processor on board... Good modern programming practices suggests that one should always multi-thread...
One of the things I like about the Be OS is that apps using the standard Be libraries get a lot of threads for free: all the UI stuff gets its own thread, for example. I'm pretty sure that OS X doesn't provide this degree of auto-threading...
I don't know about this, but I would guess that if it is only a matter of librairies, then this situation can be easily improved upon at a later date by updating the librairies... This will be easy to do since the librairy architecture (framework) in OS X is so adaptative.