Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: No "New" PowerMacs Coming At WWDC

Originally posted by Snowy_River
Okay, I guess I was too cryptic. I'll try again.
If you're tired of ex, why zee?

Originally posted by etoiles
I was not serious, just trying to be funny saying "give me zee power !" with a German accent...
Oh well, either the accent doesn't come accross too well or I am really trying too hard :D
Originally posted by Snowy_River
Yes your implied accent came across just fine. My joke is still getting lost, though. Oh well. I give up...
Gave me a laugh!
In fact I may have been more interested in reading if etoiles missed the 2nd hint than the will-it/won't-it discussion :)

So etoiles,
"ex, why zee?" eh? be see-ing U!
(I know, cheap)
 
Re: For grins, who here is actually going to be at WWDC?

Originally posted by fred_lj
I was just thinking: if there's no QTTV stream of the keynote (since it's a paid admission-type thing), are there going to be people there that will post whatever happens to sites such as this/other rumor sites?

The keynote is open to the press - the sessions are under NDA.

Btw. this WWDC will be bigger than ever because QuickTime Live! is now part of it, and there is also a new Enterprise IT track.
 
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: No "New" PowerMacs Coming At WWDC

Originally posted by GregAussie

Gave me a laugh!
In fact I may have been more interested in reading if etoiles missed the 2nd hint than the will-it/won't-it discussion :)

Good to know that it didn't get missed by everyone. :D

IMAB. RUAB2?

CU!
 
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: No "New" PowerMacs Coming At WWDC

Originally posted by Snowy_River
Good to know that it didn't get missed by everyone. :D

IMAB. RUAB2?

CU!


Oooooooookay....sorry, it was late...I am slow...never give up !
:p
 
Originally posted by jcr
jettredmont said: " Objective C/C++ is a great UI language, but its type-unsafe nature makes it next to impossible to use for a real "workhorse" or complex app!"

This is simply incorrect.

iDVD, DVD Studio Pro, Apple's Project Builder, and the Apple Store are all examples of "complex" apps based on Objective-C. I personally have worked on derivatives-trading apps for a number of wall street firms that were written in Objective-C, and we've never wished we had the inflexibility that comes from so-called "type safety."

-jcr

Okay, to each his own. That should have been prefixed with "IMHO" anyways.

I've just seen too much really bad code in ObjectiveC (almost the same ratio as in Visual Basic) to consider it a real maintainable language for non-UI work.

Regarding Apple's apps being Obj-C through and through: I'm not so sure that's the case. I mean, to start with, Apple Music Store is, if I recall correctly, run on WebObjects, which while it can use Obj-C, is more likely to be using Java these days (if for no othe reason than that Java programmers are easier to find and less expensive to hire than Obj-C programmers). Project Builder, if I recall correctly, is fundamentally C++ (one of the developers mentioned this last WWDC).
 
Re: PPC970 at WWDC 2004?

Originally posted by fpnc
Frankly, I think we'll see PPC970-based Macs shipping at a time that is almost closer to NEXT year's WWDC than it will be to June 2003. That's my totally controversial leadoff statement. :)

IMO, it will be a truly amazing feat if Apple ships the PPC970 before the very end of this summer let alone June or July 2003. Late fall or early winter seems very likely to me and it's possible that we will still be waiting come January 2004.

As for the various rumors over the last few weeks, I think that many of these have been largely debunked. In fact, the recent Arstechnica paper on the PPC970 should have placed the last nail in the coffin on those rumored performance benchmarks.

As far as configurations, I expect that we will see SINGLE processor 970's replacing the current price points, with perhaps a more expensive "ultra" option with dual-970's (and Xserves). In the meantime we will likely see a speed bump in the G4 desktops, followed by a price reduction later in the year. And, of course, we're going to see a new and improved 15" PowerBook (completely new form factor).

When the 970's arrive they should be very nice machines but they won't be setting any new price-performance marks in the PC industry. They certainly will represent a new and vastly improved phase for the Macintosh but I won't be expecting miracles (such as dual 970's at less than $2K or single-processor machines that CLEARLY outperform high-end P4-based systems on a wide range of tasks).

This is a "rumors forum", and your OPINION is yours to express, but here are a few HARD FACTS:
This is the very most "barebones system that you can currently buy at Dell right now, with only THE MOST ESSENTIAL ITEMS ADDED.

You won't find the price, (for what you get to be "so great" either:

Note: I used Xeon instead of P4 since they are dual capable, and support larger memory.

The setup below as configured will cost almost $1,900.00
Dell Precision™ Workstation 450 0Desktop: Intel® Xeon™ Processor, 2.00GHz, 512K Cache
2ND PROCESSOR (Must match speed selection above): Intel® Xeon™ Processor, 2.00GHz, 512K Cache
Memory: 256MB,DDR266 SDRAM Memory,ECC (2 DIMMS)
Keyboard: Entry Level, PS/2, No Hot Keys
Monitor: No Monitor Option
Graphics Cards: ATI, Radeon™ VE, 32MB, VGA (dual monitor capable) RADEONV
First Hard Drive: (3 Drives Max)
40GB ATA-100 IDE, 1 inch (7200 rpm)
Floppy Drive: 1.44MB FDD,Full-size,no-bezel,F3 bay-1ST SOURCE
Operating System (not as much choice as some proclaim; you get Windows, or Windows)
Dell PCs use genuine Microsoft® Windows® ONLY
Operating System: Microsoft®Windows® 2000 Professional (SP3) with Media using NTFS
Mouse: PS/2,Dell, 2 button w/no scroll
CD-ROM, DVD, and Read-Write Devices: 48X CD ROM
You'll also be FORCED to purchase....
Productivity Software: Microsoft Office XP Small Business and ADOBE ACROBAT 5.0
Hardware Support Services: 3Yr Parts + Onsite Labor (Next Business Day)
Installation Services: No Installation
Other Options: 1394 Controller Card
Intel Hyper-Threading: Hyper-Threading feature preset to "ON." Can be disabled/enabled in BIOS.
Security Software - Shipped Separately: Symantec Antivirus CorpEd 8.0 (1 user license)
Dell PowerConnect Switches: PowerConnect 2124 24-pt 10/100 +1GB unmgd w/ 1-yr NBD Parts
:rolleyes:
 
Regarding Apple's apps being Obj-C through and through: I'm not so sure that's the case. I mean, to start with, Apple Music Store is, if I recall correctly, run on WebObjects, which while it can use Obj-C, is more likely to be using Java these days (if for no othe reason than that Java programmers are easier to find and less expensive to hire than Obj-C programmers). Project Builder, if I recall correctly, is fundamentally C++ (one of the developers mentioned this last WWDC).
First, Obj-C is C. Its a runtime etc, that is built on standard C. That means, unlike VB it is a REAL PROGRAMMING LANGUAGE. If you drop down and start using functions (many standard parts of cocoa use C funtions for speed) means you can mix and match to your hearts content. A lot of people try to make Obj-C behave like C++, but its NOT C++. Dont even try, its much more dynamic than C++ or Java, you just need to work with it, instead of against it. There is a lot of bad code out there (an opinion) I guess because people don't know how to optimize things correctly, just give it some time, and dont forget that just because you use C in a cocoa app, somehow its not using Obj-C/Cocoa at its core, there the same thing, the difference is one is behaving like an object, the other is dealing with primitve data...
 
Re: Re: PPC970 at WWDC 2004?

Originally posted by tazznb
This is a "rumors forum", and your OPINION is yours to express, but here are a few HARD FACTS:
This is the very most "barebones system that you can currently buy at Dell right now, with only THE MOST ESSENTIAL ITEMS ADDED.

Xeons in a SP system? Get real. (The point of Xeons is that Intel gets to differentiate the workstation market from the desktop market somewhat more, raking in som bonus profits...) As for buying a barebones system - well, you don't get those from Dell.

Regards / GulGnu

-Stabil som fan!
 
Re: Re: Re: PPC970 at WWDC 2004?

Originally posted by GulGnu
Xeons in a SP system? Get real. (The point of Xeons is that Intel gets to differentiate the workstation market from the desktop market somewhat more, raking in som bonus profits...) As for buying a barebones system - well, you don't get those from Dell.

Regards / GulGnu

-Stabil som fan!

I think you misunderstand what I posted; You CAN purchase a xeon SP system (if that's what you want, or you can get a DP xeon (like I have), I just wanted to get the falseness out of the previous post stating that you'd get such a "fantastic buy" if you were to get a xeon system.

By the way the Dell xeon system I posted in my previous post was almost a bare bones system, and to say people won't buy them in this config is ludicrous.
 

Attachments

  • baby2 - small.jpg
    baby2 - small.jpg
    38.3 KB · Views: 637
3d on the mac

render farms are a little faster on windoz


A little faster! thats quite an ostrich impersonation you have going there. The PC by my testing ( as opposed to fabricated wishfull thinking) is over twice as fast. Here is a link to the maya render bench scene file.

http://www.highend3d.com/tests/maya/testcenter/download.3d

Feel free to try it for yourself. I have and I have found this.

This scene renders in exactly 3.00 minutes square on a dual 1.4 G4 with 1 gb of ram. It renders in 1:12 on a dual 1.5 athlon
with the same amount of memory. It renders in 1:23 on a single 2.4-P4 with half as much ram.

Add to this the fact that both pc's together where still less than the single mac plus they have been considerably more stable in our production enviroment. It brings a whole new meaning to the term "sad mac"

And yes Maya is HIGHLY multithread optimised.

Here is a link to the rest of highends test database, notice the total absence of mac scores.
 
Re: Re: Re: The pessimist -- maybe

Originally posted by fpnc
Yes, but the problem with maybe this and maybe that is that you really aren't saying much of anything. I'm willing to go on record (for what it's worth) as saying that there will be no PPC970 introduction at WWDC. By "introduction" I'm talking about an actual product demo followed by a reasonable number of shipments within 30 days of WWDC. If I'm wrong then I'll be wrong. However, if I said that there was little chance of an introduction and then they are introduced what does that mean? Was I 50% wrong, 70% wrong, mostly correct if they don't ship until after July 15? If we're going to make predictions then we might as well be bold.

So, what I'm saying is no PPC970-based Macs until at least LATE summer. No significant change in the price points over what we have today ($1500 to $2700 with ultimate well over $3000). And a likelihood of more single processor configurations replacing the existing dual G4s. That doesn't mean more models, I'm just saying that I expect that a single processor PPC970 will replace one of the configurations that is currently occupied by dual G4s.

Why will Apple move to more single processor configurations? They'll do it to maintain profit margins and to set the tone for positioning the PPC970 as a direct competitor to single processor WINTEL systems. It will also give them a buffer in case initial supplies of the PPC970 become tight. We'll see multi-processor PPC970 systems at the very high-end and in Xserves and I expect as the months and years go by we'll see more of a return to dual processor configurations, but as a general business model I think Apple would like to return to single-processor systems -- at least during the initial transition. Save the dual-970s for when and where they will really be needed.

You have a good point there. I hope Apple will make a change for the better, and offer single, and dual processor customizations.

Their choices have always been too rigid.
 

Attachments

  • baby2 - small.jpg
    baby2 - small.jpg
    38.3 KB · Views: 646
Re: Re: Re: Re: PPC970 at WWDC 2004?

Originally posted by tazznb
I think you misunderstand what I posted; You CAN purchase a xeon SP system (if that's what you want, or you can get a DP xeon (like I have), I just wanted to get the falseness out of the previous post stating that you'd get such a "fantastic buy" if you were to get a xeon system.

By the way the Dell xeon system I posted in my previous post was almost a bare bones system, and to say people won't buy them in this config is ludicrous.

Ah - sorrees. =P

But MS Office in a "Barebones system"? I'd cut that out at least.

Regards / GulGnu

-Stabil som fan!
 
Originally posted by Fukui
First, Obj-C is C. Its a runtime etc, that is built on standard C. That means, unlike VB it is a REAL PROGRAMMING LANGUAGE.

I wouldn't say VB isn't a real programming language. It is just hopelessly complex (strangely enough) for the level of power it provides the programmer.

If you drop down and start using functions (many standard parts of cocoa use C funtions for speed) means you can mix and match to your hearts content.

Today, you can mix C++ and Obj C and C to your heart's content. Time of last year's WWDC, C++ and Obj-C could not be in the same source file (and the C++ code had to have an 'extern 'C'' front-end to it). That was when the PB developer said that they were using C++ underneath an Obj-C UI layer (which was in response to a question about how feasible such a model would continue to be in the upcoming Jaguar Project Builder IIRC ... I remember this quite clearly because I had the same question for my project).

But, yes, point taken: Obj-C is just C with object-ish extensions (like C++, but in a less strictly typed manner regarding the objects). Of course, actively viewing it as such pretty much destroys the veneer of an OOPL (I have a peeve with people doing straight C in C++ when it's not performance-necessary, and the same would be true of C in Obj-C). And, yes, today C++ and Obj-C code can at least coexist in a single source code file although of course you can't be passing a C++ object to Obj-C or vice-versa (and you have to make sure your C++ headers don't use Obj-C keywords like "id" ...).

By "poorly written code" I mean code where massive bugs showed up at runtime (only when the user does 'X' then 'Y' then 'Z') which, in a language like C++, would have been found at compile time. Yes, there are also problems (memory management especially) which are more likely to show up at runtime in C/C++ than C/Obj-C (memory management is slightly "easier" with Obj-C, roughly akin to using a "smart" pointer system in C++). But, as I said, this is personal opinion here ... I really like Obj-C for the UI, and the NS UI library is about the best I've come across.

I just haven't seen with my own eyes a successful project based on Obj-C through and through, and have seen many projects (including the aforementioned from Apple) which consciously chose to use Obj-C for the front-end while coding in C or C++ on the back end.

Language war end ...
 
Originally posted by jettredmont
Okay, to each his own. That should have been prefixed with "IMHO" anyways.

I've just seen too much really bad code in ObjectiveC (almost the same ratio as in Visual Basic) to consider it a real maintainable language for non-UI work.

Regarding Apple's apps being Obj-C through and through: I'm not so sure that's the case. I mean, to start with, Apple Music Store is, if I recall correctly, run on WebObjects, which while it can use Obj-C, is more likely to be using Java these days (if for no othe reason than that Java programmers are easier to find and less expensive to hire than Obj-C programmers). Project Builder, if I recall correctly, is fundamentally C++ (one of the developers mentioned this last WWDC).

Ok, in no particular order: I was talking about the Apple Store (you know, the web site that takes a few billion dollars in orders for hardware every year), not the the Apple Music Store.

Secondly, I'd like to know what programs you're referring to when you mention really bad Obj-C code. I think that Nisus Writer, OmniWeb, OmniGraffle, Keynote, and Create! are all pretty impressive examples.

Thirdly, Project Builder is a Cocoa Objective-C app, and I'm quite sure that nobody from the Developer tools group said otherwise.

As for Objective-C's maintainability, I can personally attest to having used it in trading-floor apps that were revised as often as nightly. I shudder to think what a nightmare it would have been to attempt the same thing with C++ or the like.

-jcr
 
But, yes, point taken: Obj-C is just C with object-ish extensions (like C++, but in a less strictly typed manner regarding the objects). Of course, actively viewing it as such pretty much destroys the veneer of an OOPL (I have a peeve with people doing straight C in C++ when it's not performance-necessary, and the same would be true of C in Obj-C). And, yes, today C++ and Obj-C code can at least coexist in a single source code file although of course you can't be passing a C++ object to Obj-C or vice-versa (and you have to make sure your C++ headers don't use Obj-C keywords like "id" ...).

Right, since Objective-C is really C, I mean really C, you could theoretically program an Obj-C app in pure C, though it would be a horrendous undertaking. Yea, the Appkit is probably the best framework for UIs ever, but dont ignore the Foundation either, I think with Obj-C most people just concentrate in Utilizing the Appkit, but the Foundation is also very very powerful. And just because you use C to implement a method doesnt mean an object cant be an object, that IMO is what is so special about Obj-C, unlike Java, C++, or C# (uses C syntax with additions, but not trully "Built in" C), it really has all the power and flexibilty of C, and is trully built on C, so i think apps with the bugs you mentioned are because people haven't really researched how things occur at runtime and consequently run into problems, IOW, they are probably just relying on the compiler checking things at compile time, and then saying, my code should be fine now like in C++ or C...thats wrong, its not final until you run it, thats all, but that is particularly what makes it so powerful (and slightly slower).

Anyways, I dont think there is any language war, its just that Obj-C is so different people aren't used to it.
 
Re: 3d on the mac

Originally posted by sparkplug
A little faster! thats quite an ostrich impersonation you have going there. The PC by my testing ( as opposed to fabricated wishfull thinking) is over twice as fast. Here is a link to the maya render bench scene file.

Well I don't do 3d but I guess that's why Steve went to intel for pixar. But I think you are also putting your head in the sand, in your support for MS, maybe you remember some of the stories of their theft and MS getting sued for it? Maybe if my business relied on rendering I would think about a widoz pc...naa
I am curious why your Mac isn't as stable as a pc, that's a first!
I've been very happy with the Mac apps for the last 8 years, stability wise.
peace
daniel
 
Originally posted by jettredmont
Regarding Apple's apps being Obj-C through and through: I'm not so sure that's the case.

You do know who jcr is, right? If he says an Apple app is Cocoa/ObjC, there's a pretty good chance he's correct :) You're right that the Apple store back end is Java (being WebObjects), and iTunes is Carbon because it was originally written for OS 9. But virtually all of Apple's OS X apps, including Project Builder, are Cocoa (Finder being the most prominent exception).
 
G4i? Or... "Now for something completely different"?!?

Originally posted by Snowy_River
Well, even if Apple gives Moto the boot, I'd expect the IBM 750GX processor (G3 + Altivec compatibility) to be called a G4. Maybe the G4i, as it comes from IBM and would be used in the 'i' line? (i.e. no more G4 based Power Macs or PowerBooks...)

Honestly... Apple could pull a fast one in this instance and make this so-called 750GX (if it exists) called something <name here>, and the PPC 970 called something else <different name here>. I mean... Intel sells Celerons and Pentiums and Itaniums. Perhaps Apple, to ditch the current "G#" nomenclature, switches everything away? Hell, who knows what it'll be called... but since Apple could call Motorola's cryptic "AltiVec" the "Velocity Engine"... who knows what the next generation of Mac processors will be called?!? It depends on our favorite CEO and how creative he's feeling that day...

Perhaps they keep Motorola G4's around 'til time comes when they transition to a future PPC 9xx that is designed for portables. Lord knows the 970 has shown to have more wattage and no accoune><ff power management features (not like IBM is going to use these things in servers if they're geared mostly for laptops, and first generation chips usually produce smaller yields and have higher power consumptions 'til the chipset evolves and shrinks in die size, and efficiency efforts take place) than a Pentium M Centrino-based laptop (12-25w). The low-watt G4's in the laptops are considered hot at their current temperatures... and the high-end desktop G4's are waaaaaay too hot for laptops, and the 970 23w current falls closer to the high-end G4 30w than the low-end G4 12w; and is nowhere near the iBook G3 at 7w. Anyone have any specs on the 750GX wattages? Be curious to see... you guys might be on to something if this is indeed true and if it has speeds and wattages better than what Motorola has or will get with their G4's here soon. It'd at least buy some time 'til IBM scales the 9xx down to less intense wattages and adds some power management features to make it speedy, but also make less of a dent on batteries. I don't see IBM going hog wild on updating a G3 to be a G4, and don't see much point to it when a shrunken die PPC 9xx with power management functionality would likely drop the power down to near 12w, if not lower.

As far as licensing... IBM made the PowerPC... if Motorola sues over the chosen name, IBM can sue over the PowerPC name, which they own. I'm not saying that Motorola won't... but I'm just pointing out a genuine fact. I really think it's more of a case really where Motorola "WANTS" to get out of the desktop game now, and their contractual agreement I feel has been more than served by Apple. This would be a way to amicably split... if not on the best of terms, at least on terms that frees Motorola to pursue what they seemingly want to focus on (embedded) while IBM who uses their processor technology in a more "server" focus can now have a light-server and even workstation processor that they also sell in volumes to Apple and gain some considerable sales to offset it's development costs in servers and workstations, with consumer desktops, and laptops down the road.

The fact IBM didn't support SIMD prior because of no Linux/AIX build accessing it and being rather "unimportant" for the most part in IBM's field... tends to point to a client that talked them into it after they previously said "NO" to it at the time of Motorola and IBM splitting their PowerPC roadmaps in separate directions. Apple has invested a "TON" in AltiVec, they have the instruction calls, their OS is optimized for it, they've just gotten almost everyone except Quark (coming soon) moved over to PowerPC in OS X with AltiVec... so the logic is that:

1) Apple is not leaving PowerPC.

2) Apple is not wanting to lose AltiVec and reoptimize everything.

3) Carbon, overall, hasn't been fused with Cocoa and paired down enough or merged altogether to go jumping to any new processor.

4) AMD/Intel is not going to build a PowerPC, and Apple is not going to jump everything over to x86 this soon and start over.

5) Motorola has no G5 plans anymore... Itanium has no AltiVec-compatible SIMD, neither does AMD's Hammer... neither does Sun's SPARC. The only one that has it? PPC 970 from IBM. Why? Unless someone else is going to use it... good question... for enterprise, Vector processing isn't a major focus, and it's performance features would be "minimal" compared to hardware-based proprietary solutions that better fit enterprise and cost less time to ramp up and mfg.

The fact is... the PPC 970 client seems most likely to be Apple, as Apple has everything to lose by sitting stagnant without a processor future from Motorola (no G5), and IBM has everything to lose on PowerPC if the platform base shrivels and shrinks into nothing... as IBM's desktop G3 sales in iBooks would go out the window if Apple switched to anything but faster PowerPC's as it's "HIGHLY" unlikely that Apple would support 2 platforms simultaneously.

So, by taking the PowerPC back in at their own labs in a big way... and pulling Apple in as a customer (and IBM fits Apple better than Motorola since the axeing of clones anyhow, as Motorola has been bitter and embedded isn't something that Apple is huuuge on, with exception to laptops which are "reasonable" at 12w consumptions... even if a bit warm compared to a iBook at 7w)... IBM keeps their G3 sales for now, adds any interim processor sales to the lower-end power-conscious machines (if Apple doesn't stick with G4's for the near term in low ends... I'd expect to see something like this 750GX to be true... I'm more believing in G4's 'til next spring in Powerbooks, iMacs, and eMacs... when the 9xx efficiency model transitions in and takes over Powerbooks, eMacs, and iMacs while the iBook moves to G4, and then PPC 9xx eventually), and transitions to a new age PowerPC that helps both Apple *&* IBM in machines that "BOTH" sell. IBM focuses on producing powerful chips... Apple needs powerful chips and actually wants "FAR" more powerful chips than they've sat stuck with compared to Intel and AMD. Motorola's biggest sales aren't too Apple... but to embedded chipset customers that use them in everything from printers to automotive to consumer electronics and other gadgetry where efficient, low-power consumption processors reign.

All roads point this way if you analyze it... but how fast we're going down that road... that's where ya'll need to keep your wheels under you before you go spinning in the grass rather than staying on the tarmac. In other words... relax, take a deep breath... be cool, calm, collected, accept the reality of here and now, and don't predict the future and buy what you need when you need it.

As I've said before... will Apple release at WWDC? No telling. The Mac Creative Expo? No telling. Q1 2004? Possibility, but unsure 'til it happens. Don't get so wound up you're losing sleep over it... but rest assured that this "WILL BE" the direction Apple takes in eventuality. For how long? Uncertain... but I don't think Apple will be porting people away from a PPC-based architecture anytime in the next 5 years, and unless Motorola breaks out something wicked... and even if they do... I expect Apple to make usage of the PPC 970 as I don't see them dropping any ties if they can avoid it, no matter how miffed they are. If Motorola decides on a G5 and launches one... Apple "MIGHT" support it, but they'll never bind into a "Motorola-only" contract again.
 
Originally posted by 3.1416
You do know who jcr is, right?

Umm, no I don't. Who is "jcr"?


If he says an Apple app is Cocoa/ObjC, there's a pretty good chance he's correct :)

If he has inside information on that, I certainly defer to his knowledge. I questioned it based on a comment made in one of the Project Builder WWDC sessions last year. But certainly, I could have misunderstood the comment (although I recall it being quite straightforward) or the developer doing the commenting could have been mistaken (hey, I've been in lots of companies where dev people sent to conferences talk about things they don't fully grasp ... no one corrected him, but whatever ...) or he could have been correct that PB is Obj-C with C++ bits embedded, but not mentioned that the C++ bits are fairly inconsequential to the whole of Project Builder (which sounds more plausible than the other possibilities).

So, if "jcr" has more than secondhand knowledge concerning this, I completely cede the argument, because I only have "hearsay" ... :)


You're right that the Apple store back end is Java (being WebObjects),

Actually, I was mistaken on that one too I believe :) I misread and thought he was talking about the newly-launched iTunes Music Store, not the venerable Apple Store.

While the Apple Store is definitely WebObjects, it dates back to when WebObjects was Obj-C through and through (pre WO 5 I think ... <4.3?), and so unless the Apple Store has been fairly extensively rewritten since then (not unheard of, but far more likely that it hasn't) it's probably still Obj-C, at least the vast majority.


and iTunes is Carbon because it was originally written for OS 9. But virtually all of Apple's OS X apps, including Project Builder, are Cocoa (Finder being the most prominent exception).

Note that there is a distinction between a Cocoa app and an Obj-C app. All Cocoa apps will have Obj-C in them (or Java, in theory), but that does not mean that the app is "pure" Obj-C. A "pure" Obj-C app (1) will have its business logic is centered around an object model (ie, not strictly procedural) and (2) the core object model will be implemented in Obj-C rather than C++ or even straight C (yes, you can OOP in C, and we did so for years before Stroustroup's C++ reared up and gained legitimacy ... it's just messy ...). Yes, this can be a fairly subjective definition, depending on where you delineate between your "core business logic" and "the rest", as it is not uncommon at all to have various flavors of design mixed in to a single product.

It is very easy (and IMHO natural) to graft a "Cocoa" front end onto a core business logic centered around a C or C++ cross-platform (yes, Obj-C is cross-platform, but are there any projects that use it as such? I have a hard time trusting a compiler that hasn't been thoroughly "battle tested"!) business logic core, taking full advantage of the Cocoa services for the UI and such while keeping the relative safety of cross-platform code around the company jewels.

Sorry to all for elongating this discussion ... I'll bow out now, my predjudices regarding Obj-C having been thoroughly aired :)
 
Re: G4i? Or... "Now for something completely different"?!?

Originally posted by IVIIVI4ck3y27
Perhaps they keep Motorola G4's around 'til time comes when they transition to a future PPC 9xx that is designed for portables. Lord knows the 970 has shown to have more wattage and no power management features.
...
The low-watt G4's in the laptops are considered hot at their current temperatures... and the high-end desktop G4's are waaaaaay too hot for laptops, and the 970 23w current falls closer to the high-end G4 30w than the low-end G4 12w; and is nowhere near the iBook G3 at 7w. Anyone have any specs on the 750GX wattages?

1) We don't know if the PPC970 has power management features or not. There has been no word from IBM either way, and there is an incredible lack of information available (aside from the PDF originally presented that while informative, is at the same time uninformative). So on this front, we cannot say if the 970 as it stands will be usable in a laptop

2) You have your wattages mostly wrong. PPC970 @ 1.2Ghz is 19watts, which is a 1.1v part. G4 @ 1Ghz is either a 15w(1.1v), 21w (1.3v) or 30w(1.6v). It has been suggested that (given battery capacities for various powerbook models) that the 15" uses the 21w part, and the 17" uses the 15w part. Either way, the wattage isn't that much different between the 970 and the G4 at the same speed (the 970 is just has a higher clock frequency - est PPC970@1Ghz on the 1.1v core is 16w - just 1 watt hotter than the G4 1.1v part at 1Ghz). So no, the 970 isn't that much hotter than the G4, but it is much faster.

3) There is no information anywhere about the 750GX - it is a complete rumor at this point, as IBM hasn't announced anything about it (or if it is even in planning!)

3) Carbon, overall, hasn't been fused with Cocoa and paired down enough or merged altogether to go jumping to any new processor.

Carbon would go right along with any processor transition that Apple could think of, regardless of it's state respective to Cocoa. There is nothing in Carbon that truly ties it to a particular processor (the MacOS X implementation is completely different from the MacOS 9 implementation. There may have been shared ideas between the two implementations, but rather little shared code).

Carbon and Cocoa will eventually 'fuse', but I predict it will be more along the lines of Cocoa being redeveloped to run over Carbon. Both libraries have similar pitfalls currently, so there is probably a lot of pressure to make it work, and only do the work once. And there is no reason for Apple to build a C interface to an ObjC library when they can instead put the functionality into a C library and wrap it in ObjC (although admittedly, this will depend on which group gets the functionality developed first). So everyone out there clamoring for Cocoa everything will probably find that some day in the future that they will really be running Carbon Apps wrapped in Cocoa :D.
 
Re: Re: G4i? Or... "Now for something completely different"?!?

Originally posted by Rincewind42
Carbon and Cocoa will eventually 'fuse', but I predict it will be more along the lines of Cocoa being redeveloped to run over Carbon. Both libraries have similar pitfalls currently, so there is probably a lot of pressure to make it work, and only do the work once. And there is no reason for Apple to build a C interface to an ObjC library when they can instead put the functionality into a C library and wrap it in ObjC (although admittedly, this will depend on which group gets the functionality developed first). So everyone out there clamoring for Cocoa everything will probably find that some day in the future that they will really be running Carbon Apps wrapped in Cocoa :D.

My understanding was that both Carbon and Cocoa are fairly "thin" (Cocoa being a bit thicker than Carbon) wrappers over the Core OS X code. In other words, these are not two separate implementations, just two separate interfaces into a common implementation. Which implementation is in C (going with the BSD subsystem).

IIRC, "Cocoa" and "Carbon" are APIs, not implementations.

If this is correct, then one can imagine the functionality of both APIs perhaps being made to have more in common (although I sense that the Carbon APIs are stagnating), but one API isn't really built "on" the other, nor would such a re-architecting make sense.
 
Re: Re: Re: G4i? Or... "Now for something completely different"?!?

Originally posted by jettredmont
My understanding was that both Carbon and Cocoa are fairly "thin" (Cocoa being a bit thicker than Carbon) wrappers over the Core OS X code. In other words, these are not two separate implementations, just two separate interfaces into a common implementation. Which implementation is in C (going with the BSD subsystem).

IIRC, "Cocoa" and "Carbon" are APIs, not implementations.

If this is correct, then one can imagine the functionality of both APIs perhaps being made to have more in common (although I sense that the Carbon APIs are stagnating), but one API isn't really built "on" the other, nor would such a re-architecting make sense.
I don't think that Cocoa is a wrapper for BSD subsystem (OPENSTEP ran on Windows too and windows only utilized the BSD TCP/IP stack). It is for some objects AFAICT, but not all, and carbon, isnt that just a re-implementation of the Toolbox API from classic? Personally I would rather deal with Objects in Cocoa, and use UNIX style functions when I need speed (which cocoa does use on occasions when objects arent needed)...you could though I guess wrap carbon into cocoa objects, but looking at NSMovie (QT Movie Wrapper) as an example I say YUCK....

Apple, please do QT in cocoa!!
 
Re: Re: G4i? Or... "Now for something completely different"?!?

Originally posted by Rincewind42

2) You have your wattages mostly wrong. PPC970 @ 1.2Ghz is 19watts, which is a 1.1v part. G4 @ 1Ghz is either a 15w(1.1v), 21w (1.3v) or 30w(1.6v). It has been suggested that (given battery capacities for various powerbook models) that the 15" uses the 21w part, and the 17" uses the 15w part. Either way, the wattage isn't that much different between the 970 and the G4 at the same speed (the 970 is just has a higher clock frequency - est PPC970@1Ghz on the 1.1v core is 16w - just 1 watt hotter than the G4 1.1v part at 1Ghz). So no, the 970 isn't that much hotter than the G4, but it is much faster.

Drat, you beat me to it... But my understanding is that the 1.1v G4s are very low yeild at 1GHz, so the PowerBooks are all almost definitely running on the 1.2v 1GHz G4s, if not the 1.3v 1GHz G4s. If I'm right, then the 1.2 GHz 970 is cooler than the current 1GHz G4s in the PowerBooks. (However, that may be a big 'if'.)


3) There is no information anywhere about the 750GX - it is a complete rumor at this point, as IBM hasn't announced anything about it (or if it is even in planning!)

Actually, we do know that the 750GX exists, at least on some drawing board somewhere, as there is a document from IBM that mentions it (I don't have the url to the pdf handy right now...), but it is only mentioned in passing and gives no technical details. So, what the 750GX is is a matter of rumor, but that it exists is not.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.