| MaulerX said: There is no excuse for this. If they are going to get political and get rid of Google maps (to satisfy their thermonuclear vendetta) then they should have replaced it with mapping solution that is at least competent. This is the freaking iPhone 5 for crying out loud. What an embarrassment. |
There are actually tons of excuses for this. Some of the Maps data is user-sourced. What do you need to keep something accurate that is user-sourced?
Here's a hint... Users. iOS6 launched two days ago. The iPhone 5 launched this morning. It's going to take weeks to get enough users on the system to start ironing out some of these bugs. Bitching about it on launch day is really short-sighted. If these problems persist six months down the line, then there is a real problem to be addressed. But if Apple shores up the issues with the system in a matter of weeks, no one will even remember this happening.
Of course, it would have been nice if the system launched bug-free. But we're in reality. Large projects don't release bug-free. It's just the nature of the beast.
Or check out my new webcomic: http://selfcentent.com/
