When are you upgrading to Leopard?
By ghutchis at Wed, Sep 26 2007 7:43am
On Day 1.
45% (243 votes)
After 10.5.1 is released.
11% (61 votes)
In 1-3 months from the release.
24% (129 votes)
In 3-6 months from the release.
4% (20 votes)
In 6-9 months from the release.
2% (12 votes)
I'll upgrade, but I don't know when.
8% (46 votes)
Nope. I'm good without the upgrade.
2% (12 votes)
Other. (Please elaborate in a comment below)
4% (21 votes)
Total votes: 544



Comments
Before
I am actually going to have Leopard running *before* it is released :-)
Before
I'm also running it now (developer release) as the new features in Obj-C and Cocoa are so useful.
OK, fair enough
I thought about adding that as an option to the poll.
But I figured that most people aren't part of the Seeding program, and anyway, even some of us with developer seeds might not be running Leopard full-time on production machines until the final release.
I'm certainly conservative in upgrading my cluster until there's another bug fix release.
code bloat
I have been saying to myself that I would upgrade on day one. This was until I started reading about the amount of code bloat that is happening between 10.4.10 and 10.5. I have had a Core 2 Duo MacBook with 2 GB of RAM for 3 months now. I absolutely love the performance that I have on this thing. I often have a lot of programs running at the same time, often with simulations running in the background, without having any sluggishness. I am worried about how this will be affected when I move to 10.5.
I would like to know what, if any, system performance hits that those of you with developer seeds have seen with 10.5.
As soon as I will receive
As soon as I will receive form the Apple Developer Connection (Student membership) the OS, I will install it on my G5 and test it for a couple of weeks. If everything run smoothly, I will do the same also on my MacBook Core2Duo.
---
I'm not telling you that you should believe me. Learn the facts, and the origins behind the facts, and make up your own damn mind. That's why you have one.
agreed
cej38, I agree. Core2Duo with 2GB RAM runs extremely smoothly. Probably the nicest system I've used so far.
So, chances are I'll wait for 10.5.1
Re: code bloat
Well... I don't know who is saying there is code bloat, but on my G4 PowerBook (Yes a G4 PowerBook, 1.5 GHz, 2 GB RAM), the Leopard seeds from as far back as WWDC 2007 run FASTER than the latest Tiger. I see improvements across the board. On my Intel workstation at work it's not as noticeably faster, but that machine is extremely fast to begin with. Still there is a boost over Tiger.
This is the same thing I observer from Jaguar to Panther and Panther to Tiger. Each release of the OS (on the same hardware) seems to get faster.
Dave
Large Code vs. Fast Code
A large install (on disk) doesn't necessarily mean slow code, as Dave mentions.
For example, Tiger was shipped as two separate versions. Leopard is a Universal install -- clearly that takes more space on the install DVD.
But the bigger point is that Apple has always worked hard on making Mac OS faster and faster and that's certainly been true through Tiger. Just because you might have more libraries or tools on disk doesn't necessarily mean that Leopard won't be faster than Tiger on the same hardware. For example, modules can be loaded as needed in Photoshop, but that doesn't necessarily slow it down.
Large code doesn't mean slow code. Maybe for Microsoft, but not everyone.
thanks for comments
Great! Thanks for all of the comments. I have really been looking forward to some of the new features of 10.5. Yeah, I have not be through a major code revision since I converted to Mac, so the only experience I have had is with Wind*ws. Thus, my fear.
I will be buying on day 1. (Or as soon as my meager grad student finances allow.)
I'll upgrade my personal machines on day 1
I can't afford to risk my daily-use software (ProfCast, Interpro PRS, Keynote, and MacPyMol) not working smoothly under 10.5 so I'll upgrade my personal machines (a G5 iMac, and a G4 AlBook) to test everything out. If all goes smoothly, I'll upgrade my main machine (a 17" MBP).
The problem is that none of my test machines are Intel-based, so they aren't really good tests....
Oh well...
64 bit adds to code bloat
I think it is also worth mentioning that one reason for the 'bloat' is that Leopard will be true 64 bit across most of the libraries (Carbon excluded). This means each framework not only has Intel and PPC versions, but also 32-bit and 64-bit. That is, each framework has 4 libraries in one. This increases the disk space required for Leopard, but note that only one of the 4 libraries ever gets loaded into RAM at any one time. So performance should be comparable or better than Tiger.
---------------------------
Drew McCormack
http://www.maccoremac.com
http://www.macanics.net
http://www.macresearch.org
You won't receive anything
You won't receive anything from Apple as a free student ADC member other than freely available Software like XCode. ;-)
ADC student
I think the original poster actually refers to the Student membership: ADC student