>It's just the first iteration. Apple works that way.
Sure, all software works this way. We all know the "release early, release often" mantra. The difference is that Apple replaced functionality that many users depended upon with something completely inadequate. It'd be like Sun or IBM going in and replacing all the super specialized custom microprocessors in your server farm with experimental souped-up 386es. Sure, they're the same type of thing, and hypothetically they should serve the same function, but you don't just go out and replace completely functional stuff without at least the basics firmly in place.
It is clear that Apple released iOS Maps very prematurely, mid-development. This was stupid, and there's really no use splitting hairs about it. Some bugs or problems are to be expected, but a critical function that most of your users depend upon, that has real, serious consequences if failure occurs (lost in a dark alley, etc. etc.) ought to be better than what Apple has put out. Add to this Apple's draconian policies that forbid Google from offering "Google Maps" as a third-party app on the App Store (though I guess today it looks like they may be waffling a bit on this), and you have a very serious problem.
I guess we can say that it may be good for Android adoption. :)
Sure, all software works this way. We all know the "release early, release often" mantra. The difference is that Apple replaced functionality that many users depended upon with something completely inadequate. It'd be like Sun or IBM going in and replacing all the super specialized custom microprocessors in your server farm with experimental souped-up 386es. Sure, they're the same type of thing, and hypothetically they should serve the same function, but you don't just go out and replace completely functional stuff without at least the basics firmly in place.
It is clear that Apple released iOS Maps very prematurely, mid-development. This was stupid, and there's really no use splitting hairs about it. Some bugs or problems are to be expected, but a critical function that most of your users depend upon, that has real, serious consequences if failure occurs (lost in a dark alley, etc. etc.) ought to be better than what Apple has put out. Add to this Apple's draconian policies that forbid Google from offering "Google Maps" as a third-party app on the App Store (though I guess today it looks like they may be waffling a bit on this), and you have a very serious problem.
I guess we can say that it may be good for Android adoption. :)