I think you mean realism. All other options are optimistic.
Never have I seen such disappointing words. It's not optimistic, it's guessing, and either way, all the release dates (except March 9th and Febuary 23rd) are in Spring.
and either way, all the release dates (except March 9th and Febuary 23rd) are in Spring.
That's not really relevant. Sure Apple said several weeks ago that Leopard was still on course for a Spring release, but going by the evidence we have to hand as of Leopard's progress, I maintain that guessing at a June release for Leopard is realistic. It is optimistic to expect it before hand, and pessimistic to predict that Apple will slip and miss their self-imposed deadline of Spring.
Judging from reports we've seen I know that if it does come out before June, I sure as hell wouldn't want it installed on my computer because it'd be riddled with irritating bugs.
That's not really relevant. Sure Apple said several weeks ago that Leopard was still on course for a Spring release, but going by the evidence we have to hand as of Leopard's progress, I maintain that guessing at a June release for Leopard is realistic. It is optimistic to expect it before hand, and pessimistic to predict that Apple will slip and miss their self-imposed deadline of Spring.
Judging from reports we've seen I know that if it does come out before June, I sure as hell wouldn't want it installed on my computer because it'd be riddled with irritating bugs.
You're going by Developer Builds, not quite the same as being a Beta Build now is it?
The entire point of Developer Builds is to make their software compatible with Leopard, not to test it for bugs. If Developers are spending more time Beta Testing than compatibility testing then they shouldn't be using these builds at all. The only bug fixes Apple delivers is anything that might get in the way of making their software compatible, and for that, it's not a requirement for Safari to be suitable for browsing, but just good enough? to make any software that might need Safari compatible.
Since Leopard development is occurring exactly 2 years after Tiger development, it's straightforward to compare the development progress of the two.
I sourced data for the Tiger progress from Appleinsider via Google searching, and data for Leopard from Wikipedia.
The data illustrate that at the current rate of Leopard development, and assuming that early-400 builds will be of GM-quality (as with Tiger), that GM should be hit in mid-late May, giving time to get Leopard to retail by WWDC/end of June.
I hate to say it, but the graph does make sense and so does a late June retail availability. I am assuming, of course, that the data used is correct.
Using this info, WWDC's Leopard tracks make more sense. It always struck me as odd that developer tracks would come so far after a commercial release if Leopard was to be released in April as we all hoped.
Oh well, Waiting for Godot is a good play. I guess I can sit through it again.
Since Leopard development is occurring exactly 2 years after Tiger development, it's straightforward to compare the development progress of the two.
I sourced data for the Tiger progress from Appleinsider via Google searching, and data for Leopard from Wikipedia.
The data illustrate that at the current rate of Leopard development, and assuming that early-400 builds will be of GM-quality (as with Tiger), that GM should be hit in mid-late May, giving time to get Leopard to retail by WWDC/end of June.
Here's the graph:
Nice work Mr. H. Your graph seems to support the reports that Leopard won't be seen until June. That makes sense to me as Apple's marketing now is for buyers to avoid the hassels of vista and get a Mac. A buggy release of Leopard would only undercut that reasoning. I look for Apple to get it right and release a stable version. Vista is a stationary target and there's no reason to rush it.
When Apple announces a release period, it typically means the product will ship near the end of the release period.
Now, that said, Apple won't want any "thunder" to be stolen from one product or another. I expect OS X will come out and get it's recognition for a few weeks before the iPhone goes on sale. So I predict Leopard will come out mid-May to very early June and iPhone will go on sale at the very end of June.
When Apple announces a release period, it typically means the product will ship near the end of the release period.
Now, that said, Apple won't want any "thunder" to be stolen from one product or another. I expect OS X will come out and get it's recognition for a few weeks before the iPhone goes on sale. So I predict Leopard will come out mid-May to very early June and iPhone will go on sale at the very end of June.
I like the way you think....
With all the hordes of people that'll be trotting out to an Apple store to get a gander at the hot new iPhone (that everyone will be taking about) what better thing to have is Apple's shiny new OS (that'll get much less press) in all its polished glory with a new and elegant gui that I have no doubt will once again put to shame whatever MS thought looked good...
Or... to put it another way. It would surely be a missed opportunity if 10.5 wasn't on display on every Mac in the store when the iPhone has it's official coming out party.
Since Leopard development is occurring exactly 2 years after Tiger development, it's straightforward to compare the development progress of the two.
I sourced data for the Tiger progress from Appleinsider via Google searching, and data for Leopard from Wikipedia.
The data illustrate that at the current rate of Leopard development, and assuming that early-400 builds will be of GM-quality (as with Tiger), that GM should be hit in mid-late May, giving time to get Leopard to retail by WWDC/end of June.
Here's the graph:
Good job. I had very similar ideas, but when I look at your graph I count six Tiger builds, beginning quite lately somewhere in the 290s and ending with the GM. The first Leopard build was (relatively seen) released way before Tiger's, and the current Leopard build is already the sixth. I personally suspect Leopard to leave your "linear fit-line" now and take a steeper way (as Tiger did), being declared GM in mid-April.
It would surely be a missed opportunity if 10.5 wasn't on display on every Mac in the store when the iPhone has it's official coming out party.
Also, since iPhone runs some version of OS X, it might be safe to assume that we're going to see a lot of interface similarities between the two. You'd think that Apple would want to release the actual OS X that iPhone runs before iPhone is out there.
Also, since iPhone runs some version of OS X, it might be safe to assume that we're going to see a lot of interface similarities between the two. You'd think that Apple would want to release the actual OS X that iPhone runs before iPhone is out there.
I'm not sure why Apple would release the version of OS X that runs the iPhone. There's really no need to.
Comments
March 8th is Mine 8)
Sebastian
That's me mum's.
March 8th is Mine 8)
Sebastian
also my brother's birthday!
This coverage has been brought to you by Poll Smokin', a discontinued but hysterical production of The Daily Show.
Looks like pessimism has taken the lead
I think you mean realism. All other options are optimistic.
I think you mean realism. All other options are optimistic.
Never have I seen such disappointing words. It's not optimistic, it's guessing, and either way, all the release dates (except March 9th and Febuary 23rd) are in Spring.
Sebastian
it's guessing
Indeed. Optimistic guessing
and either way, all the release dates (except March 9th and Febuary 23rd) are in Spring.
That's not really relevant. Sure Apple said several weeks ago that Leopard was still on course for a Spring release, but going by the evidence we have to hand as of Leopard's progress, I maintain that guessing at a June release for Leopard is realistic. It is optimistic to expect it before hand, and pessimistic to predict that Apple will slip and miss their self-imposed deadline of Spring.
Judging from reports we've seen I know that if it does come out before June, I sure as hell wouldn't want it installed on my computer because it'd be riddled with irritating bugs.
Indeed. Optimistic guessing
That's not really relevant. Sure Apple said several weeks ago that Leopard was still on course for a Spring release, but going by the evidence we have to hand as of Leopard's progress, I maintain that guessing at a June release for Leopard is realistic. It is optimistic to expect it before hand, and pessimistic to predict that Apple will slip and miss their self-imposed deadline of Spring.
Judging from reports we've seen I know that if it does come out before June, I sure as hell wouldn't want it installed on my computer because it'd be riddled with irritating bugs.
You're going by Developer Builds, not quite the same as being a Beta Build now is it?
The entire point of Developer Builds is to make their software compatible with Leopard, not to test it for bugs. If Developers are spending more time Beta Testing than compatibility testing then they shouldn't be using these builds at all. The only bug fixes Apple delivers is anything that might get in the way of making their software compatible, and for that, it's not a requirement for Safari to be suitable for browsing, but just good enough? to make any software that might need Safari compatible.
Sebastian
Holey onion rings! My b-day is on May 4th!
Same as mine.
Since Leopard development is occurring exactly 2 years after Tiger development, it's straightforward to compare the development progress of the two.
I sourced data for the Tiger progress from Appleinsider via Google searching, and data for Leopard from Wikipedia.
The data illustrate that at the current rate of Leopard development, and assuming that early-400 builds will be of GM-quality (as with Tiger), that GM should be hit in mid-late May, giving time to get Leopard to retail by WWDC/end of June.
Here's the graph:
Using this info, WWDC's Leopard tracks make more sense. It always struck me as odd that developer tracks would come so far after a commercial release if Leopard was to be released in April as we all hoped.
Oh well, Waiting for Godot is a good play. I guess I can sit through it again.
I thought people might be interested in this:
Since Leopard development is occurring exactly 2 years after Tiger development, it's straightforward to compare the development progress of the two.
I sourced data for the Tiger progress from Appleinsider via Google searching, and data for Leopard from Wikipedia.
The data illustrate that at the current rate of Leopard development, and assuming that early-400 builds will be of GM-quality (as with Tiger), that GM should be hit in mid-late May, giving time to get Leopard to retail by WWDC/end of June.
Here's the graph:
Nice work Mr. H. Your graph seems to support the reports that Leopard won't be seen until June. That makes sense to me as Apple's marketing now is for buyers to avoid the hassels of vista and get a Mac. A buggy release of Leopard would only undercut that reasoning. I look for Apple to get it right and release a stable version. Vista is a stationary target and there's no reason to rush it.
Now, that said, Apple won't want any "thunder" to be stolen from one product or another. I expect OS X will come out and get it's recognition for a few weeks before the iPhone goes on sale. So I predict Leopard will come out mid-May to very early June and iPhone will go on sale at the very end of June.
When Apple announces a release period, it typically means the product will ship near the end of the release period.
Now, that said, Apple won't want any "thunder" to be stolen from one product or another. I expect OS X will come out and get it's recognition for a few weeks before the iPhone goes on sale. So I predict Leopard will come out mid-May to very early June and iPhone will go on sale at the very end of June.
I like the way you think....
With all the hordes of people that'll be trotting out to an Apple store to get a gander at the hot new iPhone (that everyone will be taking about) what better thing to have is Apple's shiny new OS (that'll get much less press) in all its polished glory with a new and elegant gui that I have no doubt will once again put to shame whatever MS thought looked good...
Or... to put it another way. It would surely be a missed opportunity if 10.5 wasn't on display on every Mac in the store when the iPhone has it's official coming out party.
Dave
I thought people might be interested in this:
Since Leopard development is occurring exactly 2 years after Tiger development, it's straightforward to compare the development progress of the two.
I sourced data for the Tiger progress from Appleinsider via Google searching, and data for Leopard from Wikipedia.
The data illustrate that at the current rate of Leopard development, and assuming that early-400 builds will be of GM-quality (as with Tiger), that GM should be hit in mid-late May, giving time to get Leopard to retail by WWDC/end of June.
Here's the graph:
Good job. I had very similar ideas, but when I look at your graph I count six Tiger builds, beginning quite lately somewhere in the 290s and ending with the GM. The first Leopard build was (relatively seen) released way before Tiger's, and the current Leopard build is already the sixth. I personally suspect Leopard to leave your "linear fit-line" now and take a steeper way (as Tiger did), being declared GM in mid-April.
It would surely be a missed opportunity if 10.5 wasn't on display on every Mac in the store when the iPhone has it's official coming out party.
Also, since iPhone runs some version of OS X, it might be safe to assume that we're going to see a lot of interface similarities between the two. You'd think that Apple would want to release the actual OS X that iPhone runs before iPhone is out there.
Also, since iPhone runs some version of OS X, it might be safe to assume that we're going to see a lot of interface similarities between the two. You'd think that Apple would want to release the actual OS X that iPhone runs before iPhone is out there.
I'm not sure why Apple would release the version of OS X that runs the iPhone. There's really no need to.
Sebastian