Originally posted by JLL
And yet Adobe releases x.0.1 updates for most of their apps shortly after release.
It's all politics. Apple had to release something to show results and to get the developers started in porting their apps.
Those 4 weeks won't make Tiger perfect. Perhaps they would have fixed a couple of bugs, and perhaps the code they are putting into the tree now for the 10.4.1 update breaks new stuff that means that they won't be able to release Tiger within their 2H time frame.
Releasing Tiger before WWDC makes perfect sense since developers have a chance to use the final version before attending the sessions.
Sometimes Adobe releases a point update quickly. The last time they did so for Photoshop was because they somehow forgot to remove the GM timeout code.
CS 2 has an installation problem sometimes because of an OS bug that causes a timeout in the installer when formatted text is left in the clipboard.
Developers have the final release, they don't need a boxed version on the shelves. They've been working on their programs for months.
Let me give you an idea of what I'm talking about. That is, why pros are concerned with every new release.
When 10.3 came out, there was a major flaw that affected every commercial photo (such as mine) and print house out there.
Apple broke SCSI. Pure and simple. Yes, drives still worked, so those who had them didn't always notice a problem.
But SCSI based scanners and printers didn't. Now, inexpensive scanners haven't used SCSI for some time now, and so home users may not noticed this either. But if you had a scanner at home that was older, and did work through 10.2, you probably found that it didn't work in 10.3.
People in that position usually blame the manufacturer for not updating their drivers, and thus not supporting the new OS. But that wasn't true. It was the OS that was broken. This didn't just affect low price Umax and Microtek units, it also affected my $30,000 Creo. Not Good.
My Fuji Pictography 4500 also wouldn't work. Every time we tried to print, it would go well, and as soon as the transmitting window closed, we would get a kernel panic. Nothing Fuji could do worked. Fortunately, they had come out with a $275 SCSI to Ethernet adapter that let us use it, but SCSI is more than twice as fast.
We ended up using our scanners on a 10.2 machine that we didn't upgrade. This problem exists through 10.3.8.
By the way, Firewire just isn't effective with high end peripherals. Manufactures, in response to my questions, reply that they have tried, but there are too many problems.
Of course, the question here is whether Apple cares about this problem, which is serious, or that it was deliberate. Apple has been trying to move us off SCSI for a while now.
I don't care how many bugs MS releases in their products. I am a confirmed Mac user, and intend to remain that way. Apple has an uphill battle.
Ever since Jobs, a few years ago, when he came back, announced that the enterprise wasn't his customer, the largest dumping of Mac's occurred in that sector since the '95 fiasco.
Now that he is trying to get them back, the better the product, the faster it will happen.
I don't know why some think that an update every two months is ok. It's not. Every six months, maybe. Look at all the problems XP2 has caused. Do you know that only 40% of business's have even upgraded to XP from 2000? and that only 25% of XP business's have gone to XP2? MS is now going to force it. A lot of protest there.
The same thing is true of Apple's business's. Only about 50% have gone to 10.3. There's no rush.
Unfortunatly, I have to leave for a few hours, so I won't be able to respond.