I'm not sure what you're missing here...
If I write an app with the latest version of Obj-C, which runs faster than the older versions, it won't work in Xcode 3, and won't compile for PowerPC.
In order to write code that would compile on PowerPC, I'd have to use an old version of Obj-C.
This isn't just "I'll leave out optimizations for PowerPC." Newer versions of Xcode have you write entirely different code that won't work on PowerPC and doesn't back port. These aren't optional nicities.
This whole line of thinking is hilarious. Optimized code? Where? Since
when have we seen code get faster and more optimized over time as a whole? In practice (speaking as someone whose first computer was Commodore Vic-20 and who has been around to see the home computer industry develop in its entirety), I've seen just the opposite. As time goes on, hardware gets faster and faster and code gets sloppier and sloppier, slower and slower, less optimized and taking up obscene amounts of space, often with very little improvement to justify it overall at any given stage.
I mean what was so much better in Office 2008 over Office 2004 to explain why Office 2008 (with Intel code) ran slower than Office 2004 ran under emulation through Rosetta? I mean seriously. That's just 4 years. I remember when my Amiga 500 could run a WYSIWYG word processor with 1 Meg of ram with no problems or when a lowly C64 could produce professional looking documents with a whopping 64k of ram, not to mention thousands of games that were more fun than half the crap put out today that is all eye candy and little gameplay.
Was Leopard faster than Tiger? No. Was Snow Leopard faster than Leopard? No. (and that one is particularly funny since it was supposed to be an "optimized" version of OSX) Is OSX getting slimmer with each release? Is its ram requirements going down? So exactly where is this so-called "optimized" code at? Why was Leopard literally half the GUI speed of Tiger? How is that improved or optimized? You didn't notice? Yeah, if you bought a new computer with it, I guess not.
I've seen improvements in Safari for Javascript, but it seems that's all people look at. I guarantee that other aspects of Safari have been getting slower with every release. It's much more noticeable on a PowerPC machine because it doesn't have as much CPU power to waste. Things take longer to scroll while loading. Windows take longer to draw. It takes longer than it used to for my home page to come up (apparently other things are loading), etc. That's optimized?
Frankly, I watch how long it takes my MBP with dual-core 2.4GHz CPUS to draw an average web page today and think back about how web pages using simpler methods achieved the same information delivery and yet could run on a 25MHz 68030 with 18MB ram (i.e. my Amiga 3000) just fine. I can only imagine how information could come up literally instantly if all that newer unnecessary CRAP weren't on every web page out there.