Excalibur
Registered
Originally posted by terran74
Since Darwin is based on a mach kernel, making it run on a different platform is the biggest hurdle in getting apps to work on it. The nice thing about Mach is that "in theory" you could essentially have it so that when you compile a binary it compiles FAT for both platforms with no rewrite of code.
The technology has been there all along. If we remember, NeXT ran on x86 and 68k. You used one binary for both platforms because they were compiled FAT. If darwin was based on a monolithic design then there would be issues in converting apps from one platform to another.
Oh yeah, and moving to x86 would be easier in this regards because darwin already includes the necessary information to compile x86/PPC FAT binaries.
Does anyone know if the current core unix binaries are FAT in the darwin distrobutions?
This is not exactly the same OS as the NeXT days anymore. OSX now has carbon APIs. Unless an app is complete cocoa it will need to be updated to run across another cpu (x86) to address that. Also Aqua and the top layer will need to be rewritten and you can forget about classic. Being we still need classic for teh transition already in place this will be a mess to bring in porting to new hardware at this time. You saw how long it took developers to make that converstion to carbonize apps just for OSX alone. To do that they are running on carbon APIs and for some apps both. We will be in the same loop we are in now as far as waiting for companies to recarbonize apps to run on an x86 processor. I don't think that will work out for us much, because we will be in ANOTHER transitional period with people are already crying about as being too long. I'm sure companies do NOT want to go through that deja vu.
I do agree Motorola has to go, but the move to x86 I don't think is the answer. I think Apple is better off teaming with IBM, because they know the architecture and IBM can meet demand, unlike Motorola. Sure me would have to ditch Altivec, but we gain the potential for a much better process which can run fast enought to negate that loss.
Just my 2 cents...