Sure it did. Mapquest. Paper maps.
Furthermore, Apple's Maps doesn't replace anything, either. You still have access to dozens of different ways to find directions.
Blah blah blah blah, meaningless corporate jibber-jabber which denigrates your company. By giving the "problem" *even more* attention, you've made an even larger issue out of it. Those who didn't really notice or care will now *really* apply the microscope. The issue was already resolving itself and Cook turns into a pu**y.
I hope this is the last time I get to read such idiocy from Apple's CEO.
It's not idiocy at all and it doesn't make a bigger issue out of it. As has been explained before, ignoring the issue simply cause the iHaters to be even louder.
Besides, I suspect that Cook has access to better PR advisors than you.
Then you just wasted a lot of electrons. I don't think there's ANYONE who has said that there's nothing wrong with iOS. There are quite a few (like me) who say that it does have problem, but that no one has established that it's any worse than Google Maps. There are others who say that it has problems, but that's to be expected in a v 1.0 product and it will get better. But I haven't seen a single person who says that it's perfect.
So please crawl back into your hole and take your ridiculous formatting with you.
Well, I should report that iOS 6's maps can finally return a result when I search for my street, which has been charted on the map since day 1 in the beta, BUT only if I type its name with a cedilla and a circumflex to match the exact spelling (this street is named after a city in Mozambique; my entire neighborhood's streets are named after cities in Africa, meaning lots of non-ASCII characters in street names), and EVEN THEN it still points to a location like 3 kilometers away from where I live (and 3 kilometers away from the place where the street is charted on the map, demonstrating lack of parity between the map and the database). Forget about abbreviations, incorrect spelling, or missing accentuation marks; any of those will still cause the search to fail. The fact that an app is pushed to production in this state is a demonstration of pure incompetence, I wouldn't even accept this from a newbie developer.
EDIT: Added trivia about my 'hood's street names.
That's nice. So why should anyone care?
I'm still waiting for you to provide evidence that Apple Maps has any more errors than Google Maps. So far, you haven't provided a shred of evidence to back that assertion. I'm also waiting for you to provide the minutes of the meetings between Apple and Google since you repeatedly made claims about who was at fault that could only have been made if you were present at the meetings.
If they wait very long, they might as well not bother. Apple Maps is already very good and the rate of things being fixed will improve over time. Furthermore, the noise about this issue will die down pretty quickly.
Even today, the majority of people don't have any problem with Apple Maps. When Google releases their own app, it will be a 1.0 product, as well, so they may have some of the same startup problems. At that point, the only people who are likely to use the Google App are the rabid Apple-haters -- and most of them are already buying Android phones.