Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
mstecker said:
Huh? Carbon code is just as easy to compile for x86 as Cocoa code. Just hit the magic button and it's done. Now Adobe does have some challenges - likely porting from CodeWarrior to XCode (2 developers for 2 weeks tops), porting all of the custom altivec code (probably not too hard because they already have the intel optimized code for the Windows builds).

This is - for some reason - a fallacy that I've heard over and over about the x86 transition. Carbon code will recompile and run on x86. New apps can be written for x86 using the Carbon APIs.

Matthew

Matthew, you either have no idea what you are talking about or you know much more than I do. Granted, I'm not much of a developer but it was Apple that told me at WWDC that Carbon libraries won't be supported in Universial Binaries. This was part of the reason why Apple is making people move away from Codewarrior, because you have to write in pure Cocoa and for some reason I didn't catch XCode was more applicable.
This is what Apple says about Codewarrior..
"Move your application from CodeWarrior to Xcode and be ready for Intel-based Macs."

I'm trying to find some information at Apple's dev site but it's pretty vague. Carbon is mentioned in the transition documents as if it were a valid set of libraries for Univeral apps so perhaps you are correct (maybe something changed since wwdc). However, at least one Apple doc says that to compile Universal binaries, you need to be in a certain group.. those that have cocoa, carbon, java.. apps that compile already and it goes to list another group with Win32 apps that compile already so that document isn't saying that Carbon is supported natively but rather that you can port from Carbon (and Win32) to make universal binaries.

Honestly, I'm not sure. I do remember, clearly, Apple saying that Carbon would not be a supported API anymore while I was at WWDC. ((I'm much more of a sys-admin than a developer so I don't have very good first hand knowledge on these matters))

ffakr.
 
ffakr said:
Honestly, I'm not sure. I do remember, clearly, Apple saying that Carbon would not be a supported API anymore while I was at WWDC. ((I'm much more of a sys-admin than a developer so I don't have very good first hand knowledge on these matters))
Apple said that Classic would no longer be supported. Carbon is.

Check out this developer document - it says a universal binary can be made in cocoa, carbon, java....
http://developer.apple.com/documentation/MacOSX/Conceptual/universal_binary/index.html
 
Daveway said:
Why all the talk about Adobe not releasing Intel versions until 2007? Chizen stood on stage at WWDC and said Adobe would be first in line with a new suite of application just like with the OS X transition.


Adobe came out several months ago and announced that they would not be releasing an OS X x86 native version of the creative suite until late 2006 or early 2007. Adobe's CEO who made the announcement claimed that the transition would be much more difficult than SJ let on up on the stage and that Adobe would have to do extensive testing, debuging, etc which would not allow the new x86 version to make it into the next product release cycle.

Obviously you were sleeping during the last couple of Apple OS transitions. This is nothing new. First SJ comes on explaining how it will work. Then Apple releases a partially implemented solution (in this case new hardware) Next developers either get their updated product to the Apple platform or they drop Apple software development altogether. Finally Apple releases their own version of any necessary software to fill the gaps where developers desert. Hopefully we won't lose too many developers this time around.

We are already going to lose all of the legacy classic applications, thats a given. Oh well who needs education software anymore anyway. Apple already lost that battle too.:mad:
 
aegisdesign said:
Nope. It's cheaper because it has a fraction of the transistors and is made using a cheaper process than the Intel CPU.

I know it's the Intel-fanboy way now on MacRumors to describe the Yonah architecture as the next generation but such revisionism is ridiculous. The Pentium-M is a revised P6 core dating from before even the G4. Tacking on a 2MB cache and a fast front side bus doesn't change the fact it's still a dinosaur in comparison to the PowerPC architecture.

It's just a pity the implementations of each architecture haven't kept up with the marketting hype.

I am no Intel fanboy...but whatever...

I said outdated becasue it is not new, so no matter how good it is fesh bread alwas sells better than yesterdays ;)
 
ffakr said:
Matthew, you either have no idea what you are talking about or you know much more than I do. Granted, I'm not much of a developer but it was Apple that told me at WWDC that Carbon libraries won't be supported in Universial Binaries.
I don't know for sure, but I think it has more to do with CodeWarrior being phased out and not supporting compilation for Intel. I can't imagine Apple is demanding everyone rewrite their apps in Cocoa, no way in hell Adobe or Microsoft will be doing that anytime soon. I have to believe Carbon will be supported for universal binaries, especially since Cocoa uses the Carbon frameworks extensively under the hood.
 
I'm in

I currently use my powerbook G4 connected to my 23 inch apple monitor. While the set up is fantastic, I am really in the market for a desktop so that my laptop can go back to being a laptop. If it has a dual core yonah, bluray dvd recorder and hard disk- I am going to buy. Anything under a 1000 euros and I am in.

Unrealistic???:confused:
 
Bye Bye Baby said:
I currently use my powerbook G4 connected to my 23 inch apple monitor. While the set up is fantastic, I am really in the market for a desktop so that my laptop can go back to being a laptop. If it has a dual core yonah, bluray dvd recorder and hard disk- I am going to buy. Anything under a 1000 euros and I am in.

Unrealistic???:confused:

For 2006 I think it is, but if you have the patience to wait untill 2007...
 
The Yonah release has been confirmed for January - it's in press releases being picked up all over the place...

TM
 
AidenShaw said:
It's going to be an interesting keynote....

Indeed. This is going to be another one of those great situations where, potentially, Jobs is going to have too much to announce, and it will be interesting to see what actually gets announced during the Keynote. Intel iBooks, Intel Mac minis, Intel PowerBooks, iLife 06, iWork 06, new displays, iPod stuff, some insight into Leopard... what will it be? :cool:
 
ffakr said:
Matthew, you either have no idea what you are talking about or you know much more than I do. Granted, I'm not much of a developer but it was Apple that told me at WWDC that Carbon libraries won't be supported in Universial Binaries. This was part of the reason why Apple is making people move away from Codewarrior, because you have to write in pure Cocoa and for some reason I didn't catch XCode was more applicable.
This is what Apple says about Codewarrior..
"Move your application from CodeWarrior to Xcode and be ready for Intel-based Macs."

I'm trying to find some information at Apple's dev site but it's pretty vague. Carbon is mentioned in the transition documents as if it were a valid set of libraries for Univeral apps so perhaps you are correct (maybe something changed since wwdc). However, at least one Apple doc says that to compile Universal binaries, you need to be in a certain group.. those that have cocoa, carbon, java.. apps that compile already and it goes to list another group with Win32 apps that compile already so that document isn't saying that Carbon is supported natively but rather that you can port from Carbon (and Win32) to make universal binaries.

Honestly, I'm not sure. I do remember, clearly, Apple saying that Carbon would not be a supported API anymore while I was at WWDC. ((I'm much more of a sys-admin than a developer so I don't have very good first hand knowledge on these matters))

ffakr.
CodeWarrior will die after the switch to x86, along with any applications that continue to use it and refuse to switch to Xcode. Xcode is making everyones life easier, not harder. I hope that we don't lose any applications in the transfer, and that they all switch to x86 platform successfully. I know that the Classic applications will be gone forever. Running an OS 9 emulator on top of Rosetta is just silly.
 
Mercury New story

http://www.mercurynews.com/mld/mercurynews/business/technology/13405513.htm

"Posted on Wed, Dec. 14, 2005

Will Intel's Napa chip run Apple laptop?
By Dean Takahashi
Mercury News

Intel announced Tuesday that its new line of chips will be built into more than 230 new laptop computers coming in 2006, making them much better at running music, movies and other digital media.

But it wouldn't say a word about whether that includes the laptop creating the most buzz, expected from its new marquee customer, Apple Computer."
 
AidenShaw said:
It's going to be an interesting keynote....
Perhaps the most exciting. Keynote. Ever. I can't recall another past MWSF event that's causing this much buzz, except maybe the premature leakage of the PM G5 specifications.

A pressing question would be, will Mac Rumors be able to withstand the huge traffic this upcoming MWSF?

But the most pressing question of all is, will AidenShaw be celebrating the holidays? aidenshaw.jpg :p :D
 
Randall said:
CodeWarrior will die after the switch to x86, along with any applications that continue to use it and refuse to switch to Xcode. Xcode is making everyones life easier, not harder. I hope that we don't lose any applications in the transfer, and that they all switch to x86 platform successfully. I know that the Classic applications will be gone forever. Running an OS 9 emulator on top of Rosetta is just silly.

Is Codewarrior created by Apple too?

I have this impression that there isn't a real transition path from codewarrior to xcode.
 
generik said:
Is Codewarrior created by Apple too?

I have this impression that there isn't a real transition path from codewarrior to xcode.

No CodeWarrior is created by Metrowerks. But it's not being pulled over to x86, nor will it ever be.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.