Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Back to square one. That depends entirely on why and how the memory usage is reduced. Even neglecting specifically optimized hardware performance for a moment, if it is more efficient virtual memory management (likely, given that memory-consuming resources are largely non-executing modules), it will be hamstrung by PPC's poor bus performance. Any advantage would be eliminated and could even worsen performance (almost certainly on the G4).

Yes the G4 has poor bus performance, but the G5 systems had the best FSB up until the very latest Mac Pro. The G5 systems FSB is still better than the entire laptop lineup and the iMac.

My obsolete G5 has dual 1Ghz FSB busses; somehow I don't see that as poor bus performance. (the Quad 3Ghz G5 systems have dual 1.5Ghz FSB, almost as fast as the latest MacPro!)

You should have said the slow memory performance of the G5, but then again dual 400Mhz DDR memory isn't all that shabby.

Office 2008 sucks because Microsoft couldn't code a "Hello World" program without it using half the system resources. ;)

-mark
 
Huh? :confused:

Can you back this up?

Sheesh; is sarcasm dead these days. *sigh*

Office 2008 is not fast. You would think that the amount of time that Microsoft has spent coding for x86 that maybe the MBU might have spent some time looking at the Office 2007 code for Windows (at least the basic meaty parts of the code); obviously everything from input to screen drawing is way different, but man Office 2008 is sluggish.

-mark
 
This is the kind of compiler fix I'm talking about. Both result in the same optimized machine code. Two different fixes that will end up with the same result.
That's just one kind of problem, and a contrived one, at that. Not all code works that way. Tackling the code and the compiler are not completely interchangeable. Not all problems can be addressed in either way, and in fact, most can't.
But if they're working on universal binaries they will still be testing on 10.5 and PPC even though it may not be necessary if their fix is only going to be a speed/stability upgrade.
What? If their own fix is a speed/stability upgrade, then it has to do with their own code, not Apple's.
I realize that, but now you have to test 10.6 Intel, 10.5 PPC and 10.5 Intel.
No, you'd have to test 10.6 Intel and 10.5 PowerPC. If it works on 10.6, it works on 10.5--that's the whole point of a "no new features" release. Apple cleans up its shop. Developers can take advantage of those improvements without breaking compatibility with 10.5. They are reworking the lower-level calls of the OS.

Without new features, there's no need to change your code to stay current. If you are rewriting your own code, there's no reason it'll break. You're treating this like the other OS updates despite having been specifically told by Apple that this is different.
What if I wanted to make a 10.6 only app?
Just do it.
Why was it not announced that 10.6 only apps do not need to be universal?
10.5 apps don't need to be universal. Neither do 10.4 apps, if you want to get right down to it. If you don't want to support PowerPC at all, you don't have to, right now, today.
And by all means 10.6 should be a new feature release as well if we go by historic example.
Well, apart from the fact that they've explicitly said it is not, mooting the point, OS X history has precedent: 10.1.
The death of the PPC OS should be a bigger deal than that. It just doesn't seem like the kind of move Apple would make for fear of angering developers.
There's no need or point in making an announcement this early--all the underlying technologies and improvements don't even exist yet. There's plenty of time for an announcement before a working, reasonably static build arrives--months, probably. Even calling 10A96 a beta would be an overstatement.
What's to be gained by a subtle back door announcement like this?
Softening the ground for the actual announcement. It's a common strategy in marketing and politics. You drop hints and manipulate media rumors.
 
I won't be impressed until Apple re-writes for both architectures from the ground-up using assembly. That will give them fast. :D

-mark
 
If they are going to support PowerPC with Snow Leopard, they should at least support the G5s. They still have a lot of life in them and there's no reason a G5 couldn't handle Snow Leopard. :)
 
If they are going to support PowerPC with Snow Leopard, they should at least support the G5s. They still have a lot of life in them and there's no reason a G5 couldn't handle Snow Leopard. :)
I'm pretty confident that Apple will keep a PPC G5 build, I'm not so sure they'll seed it or debug it for release as Snow Leopard. I think most PPC systems devs will move to work on PA Semi stuff ... On my pet platform (Java), the transition to Intel 64 bits (whatever the x-64-name) was done a few months ago ...
 
Reading this debate makes me think:

Does Snow Leopard really amount to a tacit admission by Apple that Leopard should have been better than it is, and that they perhaps spent too much time concentrating on the Iphone?

Snow Leopard = Yes, we released Leopard and it's bloated and doesn't take advantage of our current hardware. Give us some more money for our half-way house buggy beta version (Leopard) and then give us some more money in 2009 and we'll fix it for you (Snow Leopard)?
 
Reading this debate makes me think:

Does Snow Leopard really amount to a tacit admission by Apple that Leopard should have been better than it is, and that they perhaps spent too much time concentrating on the Iphone?

Snow Leopard = Yes, we released Leopard and it's bloated and doesn't take advantage of our current hardware. Give us some more money for our half-way house buggy beta version (Leopard) and then give us some more money in 2009 and we'll fix it for you (Snow Leopard)?

Its an admission that like windows and the classic OS before it, that OSX was becoming very bloated with legacy drivers. Considering that almost every PowerPC Mac had its own custom chipset, I don't think Mac users realize how many chipsets, it actually has to support.
 
If Snow Leopard has no new features compared to Leopard, but focuses on optimizing for present [and future] intel processors, why should it support PPC? These optimizations would only benefit intel, so if it was PPC compatible, it would simply be leopard, correct?
And for people complaining, remember that Apple has a precedence for dropping older technology fast. First the 3 1/2 floppy, now the Optical Drive. It only makes sense to drop PPC support.
Even for those who bought a Power Mac 2 years ago, the switch to intel had started well before that. You knew what was coming, and the risks involved in shelling out that kind of money for hardware that was very obviously going to be complete revolutionized


I can make this rant because I own an Intel : )... I'd be pretty #@%!ing mad too
 
Its an admission that like windows and the classic OS before it, that OSX was becoming very bloated with legacy drivers. Considering that almost every PowerPC Mac had its own custom chipset, I don't think Mac users realize how many chipsets, it actually has to support.

Hmm. I think I'm going to stick with Tiger. It's so stable on my 2.0ghz dual G5 and supports all the editing software I need. And my machine is still really fast.

This is one of those non-technical unscientific "voodoo" statements which occupy 95% of these forums, but I've always thought of Tiger as being written to do the best job possible for the PPC, Leopard less so.

& on early versions of Leopard I've had crashes...and if the rumours are true, the "upgrade" path to Leopard is going to ultimately lead to a dead end for PPC users.
 
Since I have never used Tiger, my first experience with OSX has been with Leopard, I have to say if this is their worst build then it is 10times better than anything Microsoft have come up with.

If they can improve on this then good for them :)
 
Intel was sued over the Hyper-threading; they stole the idea from Intergraph; but they did settle.

From my experience, being sued or threatened with a lawsuit by Intergraph does most definitely not mean that a company has done anything wrong. And the idea of hyperthreading is quite obvious (I think the PPs on a CDC 6600 did that in the late 60s, early 70s), it is the implementation that is the problem.
 
For someone who claims to know a lot about microprocessor architecture, stating that Grand Central is evidence of "scrapping" single-core Intel is downright idiotic.

You clearly cannot tell when someone is being facetious. The reason you cannot tell is because you haven't been reading anything, but skimming things just enough to write your next rant.

THAT claim was made by someone on here as proof that PPC will not be supported (i.e. Snow Leopard will require multiple cores so that leaves out PPC users). THAT was the stupid claim (I had a dual CPU G4 and there are plenty of dual and quad G5's out there so it made no sense to begin with regardless) and that was what he was pointing out again here. Just because something NEW is supported, that doesn't mean something old will not be supported.

So Apple releases an initial developer version of Snow Leopard without PPC support yet they make no announcement that PPC support has been dropped. One can either jump to either yes or no conclusions by that evidence OR they can conclude Apple either hasn't decided for certain yet and is watching for outcry versus no outcry to steer which direction they ultimately go (in which case threads like this help PPC's case).

The main point is some of us have said we DON'T KNOW if Apple has dropped it for certain or not, but that those like youself that claim is has with no uncertainty what-so-ever are simply making things up based on ONE THING and that's the first developer release for Snow Leopard doesn't have PPC support. All the rest is ranting on about how stupid the rest of us for not jumping to conclusions. Someone ranted very loudly that "OSX 10.6 will *NOT* be called "Snow Leopard" people!!!" and yet that IS what it's called. People said leaked iPhone molds were wrong. Some were wrong. Some were right. The whole point about speculation is that it's conjecture. But people like yourself don't see conjecture. You only see black and white. It's right or it's wrong. There is no conjecture. Could you give me the lottery numbers for tomorrow while you're at it?

So? You need two machines anyway.

Have you heard of Rosetta? It means an Intel owner can compile their app for PowerPC and TEST it via Rosetta on the same machine. You don't need two machines on 10.5, Captain.

Regardless, I've seen plenty of software out there that was compiled for a given OS or platform, but plainly says the author had no way to test it on that configuration so use at your own risk. Beta-testers can help there as well.

But even so, that is the main reason there is so much software for MacOSX that doesn't work on older OSX releases. There are entire sites that list compatibility by OSX version. There are already apps out there that don't support 10.4 simply because said author doesn't have 10.4 and so he doesn't CARE if it could or would work. He simply denies it to work under 10.4 and that's that. Snow Leopard will be the same way. You'll get new users that buy machines that have 10.6 on them and they, not being major corporations that care about maximizing the user base for x amount of time will simply not include support for 10.5 because they don't own 10.5 or because the first beta they posted works under 10.6, but crashes under 10.5 and they don't want to get a hold of 10.5 or open their source to fix it.

OS9 still works fine on my 1.8GHz 7448 G4, but that doesn't mean I can get software for it. Whereas, you can still get Firefox3 for Win98 (that is older than OS9). That's the difference between Mac and PC operating systems. There aren't enough users for developers to CARE on the Mac whether it supports older systems or not.

OS X and OS X iPhone are not identical.

Wow. We've got Sherlock Holmes here! Guess what? It's STILL OSX. It's not OSX Portable like Windows Mobile (which is NOT Windows). It's STILL plain old OSX with some extra unused stuff removed.

The desktop-class development seed has never and will never contain an ARM build unless some future ARM derivative becomes a desktop processor

You don't get it at all. The point is that just because Apple has or has not given you something in a developer release, that doesn't prove the claims on here that means Apple has DROPPED IT. Whether you made the claim or not is irrelevant. Those people are on your side. I've proposed that while PPC for the desktop is dead for now, it MIGHT get used in the future in either future generation iPhones (i.e. the ARM comparison) or some new gizmo yet to be released. You cannot argue against that conjecture without claiming to be a fortune teller or an inside person within Apple that can confirm they've just dropped all development for PPC period and it'll never appear anywhere ever again. Yes, those are the claims I've seen in this thread. It's gone. It's over. It's history. It's a dead weight on the backs of REAL Mac owners, etc. It's a load of BS, that's what it is.

What you TRULY have here are a bunch of selfish Intel owners that clap and shout at the idea Apple might be doing something...anything... that might make things better for THEM. Who cares about the Quad G5 buyers from two years ago who have systems that would put the average iMac owner of TODAY to SHAME. Screw them! I'm not one of them, so screw them! Ha ha! I rule the Universe! I'm Dark Helmet! Princess Apple only loves me!

(something it's not very well suited to do). PowerPC could easily be adopted in future embedded devices and OS X iPhone could easily be developed to facilitate it.

It's not easy if they drop it internally. Yes, that was a claim in this thread. See trashed helmets above.

Honestly, each time you make a claim like this, the humor value skyrockets in your admonishing of people who "don't know" what they're talking about.

Well, the first time you say something useful instead of just condescending, I'll let you know you have gloating privileges.

Who said anything about mimicry, emulation, or anything of the sort?

Well, if it wasn't you (honestly I don't feel like wasting my time looking), someone in this thread said how great it'll be to get rid of PPC code and get Intel away from optimizations that are poor imitations of Altivec (e.g. MMX, etc.). Two of us made the point that MMX, etc., has NOTHING TO DO WITH ALTIVEC other than they are similar in FUNCTION but UNRELATED IN CODE.

The whole point is dropping PPC will NOT make Intel run faster. There is NO PPC code run on an Intel Mac. It might make future install discs smaller (well unlikely as well given it fits on ONE double-sided DVD already), but that has little to do with it it running faster or having lighter requirements. I honestly believe there are people in this thread that think Intel machines are running part of the OS under Rosetta or something. It just isn't so.

Back to square one. That depends entirely on why and how the memory usage is reduced. Even neglecting specifically optimized hardware performance for a moment, if it is more efficient virtual memory management (likely, given that memory-consuming resources are largely non-executing modules), it will be hamstrung by PPC's poor bus performance. Any advantage would be eliminated and could even worsen performance (almost certainly on the G4).

MAYBE instead of making up new tripe, they could simply optimize the crap they screwed up in Leopard compared to Tiger. Or do you think something like "Spaces" rewrote the book on the MacOS and made Leopard into the memory sucking kludge it is today? No, Leopard is the first MacOSX to REALLY increase BLOAT. Snow Leopard is announced as a bloat-killing, bug-fixing update and you assume they're going to change HOW they deal with bloat and those changes will not work on slower buses and the like.... Um, yeah. Right-O-Matey!

10.2 - 10.4 (other than Spotlight) all were faster, more efficient, less bug-prone versions of OSX. 10.5 comes along and it's a bug-ridden, memory hogging piece of bloat that was rushed out the door so Apple could get back to working on iPhone 2.x, which is their new bread and butter. So now they announce that 10.6 (instead of 10.5.xx) will fix the bugs and reduce the bloat! Well, it's about time! The whole point is it NEVER SHOULD HAVE BEEN BLOATED TO BEGIN WITH.

Now, you can point out rightly that Microsoft gets more bloated every time it releases something. That doesn't make it good programming and that doesn't mean it HAS to happen that way. Many people were disappointed in 10.5 and that's because it went from a relatively bug-free, efficient 10.4.11 to a horribly buggered, slow, memory hogging 10.5 and gained relatively few NOTE-WORTHY features in the process. The only systems 10.4.11 systems weren't completely stable on were the Intel ones. Thus, Apple's work isn't finished and hence I'm not surprised to see them announce bug-squashing measures for Intel CPUs.

There's no certainty. There are, however, several points suggesting it and exactly zero contradictory evidence.

Exactly zero, eh? I've given a list of evidence (from buying a PPC chip maker of all things, NOT announcing no PPC suport for Snow Leopard, to several articles on the Net speculating future iPhones might be PPC based). You ignore it. You call it names. You basically have NOTHING to offer here. Given your "ZERO" claim, I'd say you can't add either.

No, there are many people who believe 10.6 will end up being universal, despite all signs pointing the other way. There's nothing wrong with that. Only some of them are whining, ranting chores. A rectangle is not a square.

Why do you CARE what some people "believe". I've said time and time again, I don't KNOW if it will or not. I'm simply contradicting the BS arguments I see on here that says it WON'T *PERIOD* and don't you dare argue with the all-knowing (insert name here). I'm here to say such people don't know squat. Their arguments are based one ONE thing only and that's the first developer release of Snow Leopard doesn't have a PPC build. From THAT *ONE* thing comes all this other speculation about where OSX is going and how those technologies couldn't work or shouldn't work or will get in the way of keeping any kind of PPC support, however unoptimized for the sake of compatibility for more than 3 years since the still highly relevant Quad-G5 was sold. And even though those multi-processing technologies and smaller memory footprint, etc. would make that quad-G5 all the more relevant for years to come, it doesn't matter. They're GONE! Why can't you stupid "believers" admit it??? I could believe Apple would do it because they make most of their money from HARDWARE and they want those G5 owners to buy a new computer regardless of whether they should have to or not because it's more money for Apple. It's why they don't release a mid-range tower. They want you to buy a new iMac every other year.

No, the difference between you and me is that I don't CARE what they believe or what you believe. I'm only interested in seeing facts, not fiction. And these dramas you keep posting about how stupid people are to not admit their beliefs are WRONG ('cuz you know it) remind me of X religions trying to force THEIR VIEWS on other religions.

Instead of asking Apple if PPC support is dead or not, you'd rather rant on about how funny it is to watch PPC users wish on a star that they weren't being abandoned when the writing is on the wall. THAT is the crutch of my entire argument here. YOU don't know the future. YOU don't know jack. But you do like to run your mouth a lot, I'll give you that.
 
I'd much prefer an emphasis on speed then ppc support, those comps are getting old anyway, leopard should be fine for them
 
Is it just me or is there a slight irony that the people who slated MS for letting Vista be put on woefully underpowered computers are complaining that Apple won't design 10.6 for old hardware?

At least Apple are telling you in advance here.
 
Non-disclosure only affects those who are a party to it. Once the information is released, whether intentionally or by accident, there is no third party liability.
The details vary, but the only way NDAs really make sense in response to leaks and speculation is to "neither confirm nor deny". Just to be clear: Apple is the 1st party, WWDC attendees are the 2nd party (individually), and everyone else is the 3rd party. How does the third party liability figure into it at all?

If one attendee breaks NDA, that doesn't mean "the cat is out of the bag" and all other attendees can talk about it. A third party can lie about having inside info and just be guessing, or fabricate "evidence" to draw out the truth. The only safe thing is to simply refuse to respond. Which is a shame, since there is so much nonsense going on here.

No, you'd have to test 10.6 Intel and 10.5 PowerPC. If it works on 10.6, it works on 10.5--that's the whole point of a "no new features" release. Apple cleans up its shop. Developers can take advantage of those improvements without breaking compatibility with 10.5.
It's possible to write new code that works on 10.6 Intel, but not on 10.5 Intel, because of a bug in 10.5; or because you're actually doing it wrong, but it just happened to work in 10.6; or because there are actually different bugs in both 10.6 and 10.5. As a developer, you should test on all versions that you claim to support. Not only because that's what you're saying to your customers, but also because that increases the chance of finding bugs, which is a big reason Apple distributes seeds in the first place.

Does Snow Leopard really amount to a tacit admission by Apple that Leopard should have been better than it is, and that they perhaps spent too much time concentrating on the Iphone?

Snow Leopard = Yes, we released Leopard and it's bloated and doesn't take advantage of our current hardware. Give us some more money for our half-way house buggy beta version (Leopard) and then give us some more money in 2009 and we'll fix it for you (Snow Leopard)?
One might argue that Apple released Leopard too early, with too many bugs. Working on the iPhone was a factor; the question is how much. But, as it has done in the past, Apple is releasing 10.5.x updates for free. Will these eventually address all the problems that any particular person has? We shall see.

As far as the new "features" in Leopard versus the new "technology" in Snow Leopard, they both take time and effort to implement. It's a fallacy that you can simply hire twice as many developers and get twice as much done. It's probably not even a good idea to work on both at the same time; you simply can't focus on everything, because you end up focusing on nothing. I can easily see a situation where they were adding all the new Leopard features and coming to the realization that they really had to rework the core, an idea that may have been building for a while.

But they could have planned it this way too: one more version with a bunch of features, and the next version to rework the core. Either way, I wouldn't characterize that as "tricking" people into buying Leopard, knowing that it would be "fixed" later, because this more than just a "fix". The main question now is how to market it. If Snow Leopard enables a new generation of apps that thrive on multi-core, and just plain runs better, then it could be an easy sell.
 
And all this begins with a screenshot of the so called "specs" for "Snow Leopard".

Well guess what:
-iPhone SDK beta's are also Intel only.
-But hey, they just run great on PPC. You know why it's a so called Intel beta?
-Because the SDK runs already perfect on PPC.

iPhone SDK beta's are a good example why a spec says "Intel only".

Guess what:
Snow Leopard already runs on PPC. Snow Leopard is already optimized for PPC. That's why the beta's are Intel only.
It's so easy for Apple to code and optimize al that stuff for PPC G5.

Bottom line: Apple needs to build Intel Beta's. Not PPC beta's. They play with PPC code ;).

Just wait and see when the iPhone SDK will be out of beta ;). I'm sure this will be released as the new Xcode package ;). Oh yes, this so called new Xcode package will be Universal.

If Apple would drop PPC G5 support in Snow Leopard, they would also drop it in the iPhone SDK beta's. But in the end, all this will run on the "faster" PPC Mac. Or do you Intel geeks realy think that Apple will strip all the PPC code when the so called iPhone SDK comes out of beta? If this would be the case the SDK would not run on PPC since SDK1. This is too stupid for words! :D Realy too stupid... No PPC G5 support :rolleyes: in the iPhone SDK or Snow Leopard.... Hahahahaha...

BTW: I'm running the iPhone SDK on my G5 since beta 1. It all works fine & "bug free". New SDK beta's just add some extra features and new application builds. I love the iPhone simulator on my G5. I wonder why they just don't release it for PPC :rolleyes:. Oh yes, it's still buggy on Intel and they need to sell Intel developer machines ;).
 
That's just one kind of problem, and a contrived one, at that. Not all code works that way. Tackling the code and the compiler are not completely interchangeable. Not all problems can be addressed in either way, and in fact, most can't.

I'm not sure how you'd go about improving the speed of software, but I'd probably follow these steps.

1) Identify code resulting in poor assembly/machine code.
2) Determine the number of times that code is used in different functions.
3) If used many places, train/fix the compiler to recognize this code and use better machine language.
4) If used in only a few places, fix the code to come up with better machine language.
5) If step 4 doesn't work, fix the compiler.

Fixing the compiler to recognize different forms of code into more efficient implementations will also benefit the developers using the compiler. I'm not saying that's the only method to fix code, or even one that will be used much, but it is an option. If you can show me where I said that it will be the only method or even a predominant method please quote me.

What? If their own fix is a speed/stability upgrade, then it has to do with their own code, not Apple's.

Even if the Speed/stability upgrades utilized are part of 10.6? If I were a developer I'd want to know that PPC is dead ASAP so that I can pursue these speed/stability fixes without worrying about 10.5/PPC compatibility.

No, you'd have to test 10.6 Intel and 10.5 PowerPC. If it works on 10.6, it works on 10.5--that's the whole point of a "no new features" release. Apple cleans up its shop. Developers can take advantage of those improvements without breaking compatibility with 10.5. They are reworking the lower-level calls of the OS.

Without new features, there's no need to change your code to stay current. If you are rewriting your own code, there's no reason it'll break. You're treating this like the other OS updates despite having been specifically told by Apple that this is different.


If they're working from the OS foundations to improve speed stability there's no guarantee that code compiled in 10.6 will work in 10.5 or vice versa, you can skip the testing if you want and trust it but that's at your own risk.

10.5 apps don't need to be universal. Neither do 10.4 apps, if you want to get right down to it. If you don't want to support PowerPC at all, you don't have to, right now, today.

Well, apart from the fact that they've explicitly said it is not, mooting the point, OS X history has precedent: 10.1.

And we don't know what developers are planning for their future release. Saying CS4 or anyone else's software is a new feature release is just as much speculation as those of us saying there might be PPC support.

There's no need or point in making an announcement this early--all the underlying technologies and improvements don't even exist yet. There's plenty of time for an announcement before a working, reasonably static build arrives--months, probably. Even calling 10A96 a beta would be an overstatement.

Softening the ground for the actual announcement. It's a common strategy in marketing and politics. You drop hints and manipulate media rumors.

There is every reason to make a big announcement as early as possible so that developers, customers and users can make more informed decisions if they know via an official announcement rather than speculation based on the developer preview release requirements. If we're supposed to take those as truth where are the huge disk and memory savings since those haven't changed from 10.5?
 
You clearly cannot tell when someone is being facetious.
There was nothing facetious about it. Grand Central taking advantage of multicore communication on Intel processor and chipsets does not mean that single-core systems will not work. That would be analogous to saying that ALL software would have to be multithreaded in order to run. There's no humor in that.
to write your next rant.
You use that word, but it does not mean what you think it means.
The main point is some of us have said we DON'T KNOW if Apple has dropped it for certain or not, but that those like youself that claim is has with no uncertainty what-so-ever are simply making things up based on ONE THING
There has been no claim about certainty about its dropping. For what I can only hope will be the last time: there is a multitude of evidence that there will be no PowerPC release; there is zero evidence that it it will. Where you can conclude based on that that I've ever claimed there is no chance of PowerPC support, I do not know.

Further, "one thing" is an interesting characterization of the information thus far released. Both major features showcased are Intel-only. The system requirements state Intel only, and this bears out in installation. The current 10.6 build is not universal--the software simply does not run on PowerPC (i.e. it's not just disabled). The public announcement refers to a system overhaul, reorienting the OS for future systems (Intel systems).
Have you heard of Rosetta? It means an Intel owner can compile their app for PowerPC and TEST it via Rosetta on the same machine. You don't need two machines on 10.5, Captain.
Not if you're testing for architecture speed and efficiency improvements, which was the whole point of this melodramatic "woe is me, what are developers to do" digression. Why would your control environment include the Rosetta translation variables?

If you want to test it that way, just multi-boot. But that's not the scenario you've been advancing.
Wow. We've got Sherlock Holmes here! Guess what? It's STILL OSX. It's not OSX Portable like Windows Mobile (which is NOT Windows). It's STILL plain old OSX with some extra unused stuff removed.
No, it's not. Apple did a very good job at this year's WWDC at partitioning OS X and OS X iPhone. They share similar technologies, but are not interchangeable in the least. The desktop-class OS X is not the same. "Snow Leopard" will not run on the iPhone, just as Leopard does not now, nor did Tiger last year. The converse is also true.
The point is that just because Apple has or has not given you something in a developer release, that doesn't prove the claims on here that means Apple has DROPPED IT.
It's not "not given"--it was removed. It is unprecedented to take something away that already works and exists. When the post-Universal Tiger builds were released, and during all of Leopard development, Apple never released milestones that were incompatible with either platform.
What you TRULY have here are a bunch of selfish Intel owners that clap and shout at the idea Apple might be doing something...anything... that might make things better for THEM. Who cares about the Quad G5 buyers from two years ago who have systems that would put the average iMac owner of TODAY to SHAME. Screw them! I'm not one of them, so screw them! Ha ha! I rule the Universe! I'm Dark Helmet! Princess Apple only loves me!
Wow.
Well, if it wasn't you (honestly I don't feel like wasting my time looking), someone in this thread said how great it'll be to get rid of PPC code and get Intel away from optimizations that are poor imitations of Altivec (e.g. MMX, etc.).
No one ever said that. What was that about skimming you said?

The whole point is dropping PPC will NOT make Intel run faster.
Of course it will, by virtue of eliminating the time, effort, and compromises used to maintain the codebase, freeing up many man-hours for other tasks. New features also see significant decreases in development time, because taking advantage of hardware-specific features no longer requires the development of a PowerPC version, and improves general performance across the line by not having to do in software what more recent Macs can do in hardware.

Exactly zero, eh? I've given a list of evidence (from buying a PPC chip maker of all things, NOT announcing no PPC suport for Snow Leopard, to several articles on the Net speculating future iPhones might be PPC based).
The iPhone has nothing to do with Snow Leopard development. Whether future iPhones have PowerPC hardware in them is completely irrelevant. Lack of confirmation is not evidence, nor is speculation on the Internet. Their purchase of a manufacturer of EMBEDDED PowerPC chips has exactly zero to do with their desktop-class development.
And even though those multi-processing technologies and smaller memory footprint, etc. would make that quad-G5 all the more relevant for years to come, it doesn't matter.
Grand Central is completely useless on PowerPC. It's Intel-specific. Implementing an approximating technology isn't even possible on PowerPC except for the 970MP (the very last PMG5 revision, which represents such a tiny sliver of the Apple install base that there can't possibly be any point to investing in that development). Nothing about the measures used to reduce memory footprint has been announced, and there is no reason to expect it to be of direct benefit to PPC users.
How does the third party liability figure into it at all?
Because the implication that various posters here have broken their NDA presumes that they're the source of the information. No NDA is broken if some other party has provided the information. Even a poster under an NDA can then discuss it, as long as no new information is leaked. A developer discussing information leaked by a third party has no liability for violating that NDA.
If one attendee breaks NDA, that doesn't mean "the cat is out of the bag" and all other attendees can talk about it.
Yes, it does. As long as the party does not explicitly claim to confirm or deny the leaked material, it can be discussed in the context of speculation.
I'm not sure how you'd go about improving the speed of software, but I'd probably follow these steps.

1) Identify code resulting in poor assembly/machine code.
That right there sets you down one specific path. Poor machine code is not the only source of a speed issue.
Fixing the compiler to recognize different forms of code into more efficient implementations will also benefit the developers using the compiler. I'm not saying that's the only method to fix code, or even one that will be used much, but it is an option. If you can show me where I said that it will be the only method or even a predominant method please quote me.
In certain specific situations, it's an option. Suggesting, as you did, that it is one of two equal paths to an end in the scope of rewriting the OS generally was the problem.
Even if the Speed/stability upgrades utilized are part of 10.6?
That would not impact your code. Again, no new features. You will benefit from Apple's improvements in most cases automatically. Grand Central and OpenCL are wrinkles in that, but not enough information has been released for that to be a fruitful discussion.
If I were a developer I'd want to know that PPC is dead ASAP so that I can pursue these speed/stability fixes without worrying about 10.5/PPC compatibility.
Why would you abandon your target machine at this point? It's far too soon for that. Frankly, if you start development when 10.6 is released to retail, your product will still be finished before 10.6 achieves saturation.
If they're working from the OS foundations to improve speed stability there's no guarantee that code compiled in 10.6 will work in 10.5 or vice versa
They specifically covered this at WWDC. You can even tell just on the name: Snow Leopard does not obviate Leopard. It's not a feature release.
Saying CS4 or anyone else's software is a new feature release is just as much speculation as those of us saying there might be PPC support.
No, it's not. Adobe has already previewed CS4 and discussed a number of new Photoshop tools.

The bottom line is that any amount of foaming-at-the-mouth rage at the likely prospect of an Intel-only release isn't a death sentence to PowerPC right away. It's the next step of a long goodbye that started 3 years ago. 10.6 will not implement anything that PowerPC users will want--Apple has already said as much. I'm not talking about abstract objectives here, like speed, efficiency, and footprint requirements, that everyone wants; I'm talking about actual implemented code. It's clear from the presentations so far that even if Snow Leopard ran on PowerPC, which it does not, it's not providing any added value to PPC Macs. The code in the developer preview won't speed up or reduce resource consumption on PPC Macs.

There's no "piss off PPC users" check box that they've ticked for the hell of it. They're just developing software of use on recent (Intel) Macs. Much like Hillary Clinton's presidential nomination, it's not impossible. But it hasn't happened, and it's not in the cards today or in recent history. If it were a new feature release and Intel-only, that might be a shock. This is closer to stressing over someone who brings home an iMac with a newer build number than the one in Software Update.
 
The bottom line is that any amount of foaming-at-the-mouth rage at the likely prospect of an Intel-only release isn't a death sentence to PowerPC right away. It's the next step of a long goodbye that started 3 years ago. 10.6 will not implement anything that PowerPC users will want--Apple has already said as much. I'm not talking about abstract objectives here, like speed, efficiency, and footprint requirements, that everyone wants; I'm talking about actual implemented code. It's clear from the presentations so far that even if Snow Leopard ran on PowerPC, which it does not, it's not providing any added value to PPC Macs. The code in the developer preview won't speed up or reduce resource consumption on PPC Macs.

They've obviously been optimizing code and more efficient code would run faster on the PPC also.
 
They've obviously been optimizing code and more efficient code would run faster on the PPC also.

I don't know if this was mentioned above, but PPC G4 Powerbooks were produced until April 2006. How can Apple leave these individuals out in the cold that quickly? I know there are many arrogant intel owners who will chide me for this, but I just find it to be an odd business move personally.

I wonder why a 1.67Ghz G4 Powerbook w/ 2GB Ram is obsolete?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.