[quote]Originally posted by sCreeD:
<strong>All good points, DaveGee.
However the counterpoints are:
Software development to the scale Apple does requires schedules, milestones and testing. On some manager's calendar (or iCal, if they eat tehir own dogfood). There's a big red X that says 'Ship iSync.' And that's probably on his manager's calendar and on Steve's calendar.
Notice how they shipped Jaguar, bugs included, not just cosmetic ones either.
But we all know this to some extent. Apple, as usual, is using the vagueness of the public
ship date to their advantage.
I think iSync is going to be one of the three most important iApps Apple ships.
Oh I agree 100% and I'm sorry if I came off a bit harsh in my initial post... I tend to do that some times... (admitting it is 1/2 the battle)
But given that iSync went from being 'Released' sometime in Sept to 'Public Beta iSync' being released by the end of Sept should have told everyone that this puppy needs more time to 'bake' before it's gonna be ready.
I'm all for giving Apple the time it needs if it means we get something in a usable condition. Sure Apple could make people happy and release what they have now and say 'see we kept our word' but if the app don't work what good is it... Better to miss a deadline and have soemthing useable then to 'hit the deadline' and have a bad user experience.
Sometime (like with a Major OS update) the ship date MUST be hit NO MATTER WHAT. Since so many other things are tied to the release. With iSync (unless Apple has some hardware just waiting in the wings that totally NEEDS IT before they can sell it - and no, the iPod doesn't really count) a self imposed deadline isn't nearly as pressing.