Leopard Under The Hood And Requirements Analysis

No Photo Booth backdrops for me? No DVD Player? No Front Row? Ouch! :(

I can't believe I will not even be able to use DVD Player. That's a bit much, isn't it? Not a big deal since there are other apps I can use, but still.

With those small complaints aside, I still can't wait for Leopard. :D

Front row im pretty sure you can use (either with bluetooth, a wireless keyboard, or iphone) or networked keyboard but you just wont be able to do anything if your not at the computer. DVD player you will be able to use, just not with the deinterlacing.

What about the IR remote and an external isight?

whats the external iSight have to do with it?
 
IR was a terrible choice to begin with, it should have come with a BlueTooth remote, that way an IR sensor would not have been required thus cutting cost. :apple: is a mystery at times. :)

IR sensor likley costs apple a quarter. The remote would likely cost twice as much if it used Bluetooth, plus the battery drain would likely end up being enormous.
 
No Photo Booth backdrops for me? No DVD Player? No Front Row? Ouch! :(

I can't believe I will not even be able to use DVD Player. That's a bit much, isn't it? Not a big deal since there are other apps I can use, but still.

With those small complaints aside, I still can't wait for Leopard. :D

Please read the thread about DVD player.
 
I still can't wait

With all this being said, I don't really care how big it is, I still can't wait! Leopard is going to be sick!!!
 
New Scheduler great for quad and 8-core

I am most interested in seeing whether Leopard makes the 8-core run right.

I said in April that the 8-core was supposed to be released with Leopard, and that the horrible performance it gave was the proof.

Now that it is known that Leopard has a new scheduler, we'll get to see what the 8-core can really do when it isn't running a 25 year old scheduler. (Mach is old stuff, folks.)
 
you can save HD space on your Macbook by not installing things like various localizations and Garage Band sample loops. etc..

That in itself will save 2 gigs.
1 maybe, Garageband is not included with OS X. Though I know you already knew that.

and Tiger is not 64-bit.
http://developer.apple.com/macosx/64bit.html

There is a reason Leopard was marketed as 64bit on everything and not just 64bit.

Even if none of Tigers binaries were 64bit apps most of an OS is libraries, and since Tiger allowed both 32 and 64bit development there are both 32 and 64bit libraries in that 3GB install.
 
9 Gigs... Why is this alot?

There are hard drives now that are 1TB large. Why is 9GB such a concern?


The only people that are concerned (at least those are the only people that should be) are users like me with older machines (80GB). But yeah, I'm not gonna complain about it. 9 GB is nothing nowadays. Doesn't Vista take up about the same amount of space?
 
9GB? I'm glad I put that 250GB in my MacBook Pro. On my old 160GB, I only had 11GB free on the OS X side, and about 8GB free on the Vista side.
 
Come on Apple! You can't get a PowerPC G5 Quad 2.5ghz with 14GB or memory to add photobooth backdrops, and you can get an Macbook to do it? WTF?!?
 
but I would think that a fairly new G5 would handle this using some other codes.
I believe this is more due to the time issue. Anything can be programmed within reason. The issue is the manpower that it takes to accomplish this task.

If apple could, im sure they would drop PPC support all together, and just build Intel only (x86) code from now on.
Yes this would greatly simplify their OS model. But at the same time would alienate many PPC users who still have viable and useful hardware that are not ready to upgrade yet, but also want to run Leopard.

My guess is that the next OS upgrade will publicly be Intel only.

Apple has developed the Accelerate Framework, where one of its specific advantages is that it can run on both Altivec (for PPC) and SSE* (for Intel) without architecture-specific commands.
I think Accelerate Framework was used as more of a stopgap measure. Eventually, it will be easier for Apple to focus on one platform for future OS upgrades to tweak out the maximum performance from the available hardware.
 
Will Mac OS X 10.6 run on any G4 models? Or G5s?

Yeah, I know it's a little soon to ask, but I'm already wondering: For which of the Macs in my collection will Leopard be the last stop?
 
So my iMac will sit pretty with Leopard running under the hood whereas my PowerBook will curse the day Microsoft released Vista.
 
Will Mac OS X 10.6 run on any G4 models? Or G5s?

Yeah, I know it's a little soon to ask, but I'm already wondering: For which of the Macs in my collection will Leopard be the last stop?
My guess is that it will not.

With ZFS and other features that Apple will want to introduce, I think that it will be easier for them and developers if they focus only on the Intel platform.
 
Will Mac OS X 10.6 run on any G4 models? Or G5s?

Yeah, I know it's a little soon to ask, but I'm already wondering: For which of the Macs in my collection will Leopard be the last stop?

I would be a little sore if this dinosaur of a machine (iMac G4) doesn't run well with Leopard, but I'll accept no PPC support for the next OS because hopefully I'll have a new one by then. Hopefully.
 
9 gigs for the OS? Boo!!!!!

Piffle! I've got two 1TB disks arriving tomorrow to join the 1.5TB I have at the moment. One will become a Time Machine archive, the other becomes the system disk. The existing two 750MB drives will be my Raid 0 scach disk.

Then I've got the 2 1TB FW800 drives I use for external backups...

9 gigs isn't that much...
 
I bet this is the last version to support PPC. Universal apps will eventually disappear and one of the new secret 300 features for 10.6 is that the binaries are smaller and uses less memory.

Well speaking as a developer, Intel-only binaries would certainly be smaller on disk, but as far as using less memory (if you mean RAM), this is not true. Universal binaries are simply fat binaries. They are an archive containing separate binaries for both architectures.

For example, if I turn on both Intel and PowerPC builds in my code, it does twice the compiling and then archives both sets of object code (executable and library) into one fat binary. This is why when I'm doing incremental compiling (building and testing as I code), I'll usually just build for one architecture, because the build completes faster.

When you launch a fat binary, the operating system's loader simply picks the correct one for the machine's instruction set and the other code is ignored.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Back
Top