I believe that Carbon is a sound OS strategy, despite some non-commitments
from Apple. The most serious part of all this is that patching traps under
Carbon is a no-no, though it should still work. The Navigation Services
API is rather easy to use (download the SDK and look at the code - a lot
of "one liners" to support stuff like selecting a folder, neato open/save
boxes that have been shareware hacks, etc). Besides, Apple will undoubtedly
map calls Standard File Services to the Navigation services API in initial
releases anyway so that the OS 8 compatibility layer works.

Game Sprockets was a great idea that suffered from Apple marketing/dev
relations. The API was very sound despite some minor bugs and the NetSprocket
API was even more promising it sounded like.

As long as Apple can rip out that 10 year old "guts" of the OS without
ripping the fabric, Carbon looks OK. The "wierd" part to me is the Rhapsody
layer. Is this the Yellow box ontop of Allegro-type thing? It was my
understanding that Rhapsody was now just a great OOP application framework
so why a "compatibility layer" for it?

Ryan