Cocoa/Carbon shouldn't have too many platform specifics in it
I'm not sure exactly what you mean by this.
As for the reason, it is a market. A big one.
There's a big market for writing Windows apps on the Mac?
why do you suppose had Apple went through the trouble of keeping a separate x86 build of OS X around since day one?
Because chip availability is unpredictable.
It wouldn't be about porting OS X to Windows, which wouldn't make sense, but rather supply the upper-level frameworks. The stuff that interests the application developers.
I just don't see it. It would be a partial implementation at best and it doesn't really further Mac OS X in any way. My basic feeling is that Apple is not NeXT.
by Scott Stevenson — May 30
I'm not sure exactly what you mean by this.
As for the reason, it is a market. A big one.
There's a big market for writing Windows apps on the Mac?
why do you suppose had Apple went through the trouble of keeping a separate x86 build of OS X around since day one?
Because chip availability is unpredictable.
It wouldn't be about porting OS X to Windows, which wouldn't make sense, but rather supply the upper-level frameworks. The stuff that interests the application developers.
I just don't see it. It would be a partial implementation at best and it doesn't really further Mac OS X in any way. My basic feeling is that Apple is not NeXT.