Originally Posted by airmanchairman
Stick to the issues, like DED does; personalities don't tend to contribute anything but (negative) emotion to the discussion and are not helpful. This is key to enjoying blog sites like AI.
By way of comparison, and to explain the point being made here, count the number of uses of the word "I", "you", "my" in all posts by the author and by others responding critically to the article.
A lot of "contributors" here purporting to "portray the facts" and "uncover lies" are simply trolling professionally with a few half-truths and plenty of insults; others are trying to set the record straight and stick to the science, pushing the envelope of readers' knowledge with cool facts. The latter educate and enlighten, the former simply muddy the waters and reduce everything to a pi**ing contest of schoolboys, provoking flame wars.
A lot has been revealed here about mapping technology, both by this article and many of the constructive rejoinders written by people who are knowledgeable about and/or involved in Mapping - that's what the topic is about, not whether one is a returning Android, iOS or Windows Phone user, facts that are totally unhelpful to the issue under discussion.
Yes it really is too bad that so many AI commenters simply can't really express themselves coherently (as you do, and thanks for that) whether they are agree, disagree, or have something constructive, additional or even just a subjective opinion to add. That's really sad.
Seems like the five Android fans thought that it was critically important to write in great detail about Google's own adventures in vector maps, even though this is completely irrelevant to iOS 6 Maps because Google won't have any way to deliver its own technologies to the default mapping client the vast majority of iOS uses will be using from here on out.
And that's a really big deal, on the same level (for example) as the shift we all observed when Apple introduced MP4/AAC and H.264 as audio and video standards, killing off the proprietary WMA/WMV and ATRAC formats that Microsoft and Sony hoped to make popular. Sure, both MS and Sony contributed to those standards later, but it was Apple that shifted what everyone was using via its leverage with iTunes.
Same thing with Safari & WebKit. Everyone thought the web would always be a two horse race between Netscape/Mozilla and Microsoft. Now, those two don't even matter so much, certainly not in the mobile realm. Same thing with Flash.
The interesting point that these angry Android/Google fans are missing is that while Google may have some impressive mapping technologies (and it certainly does), it is suddenly about to lose half of the mobile device market.
And lets get real: while you can enable WebGL maps on the desktop, most people aren't using it because its a special opt in beta, and its still rather slow even on modern desktops.
Additionally, all the people going into hysterics about Google's support for vector maps on Android: that's fine if you want to argue about a pissing match, but the reality is that Google has always had 100% of the iOS maps market and virtually 100% of Android. It will soon have virtually 0% of iOS users, and 0% of iOS third party developers, which is vastly significant because iOS is where the money is made that might trickle toward Android.
Here's the first review visible on Google Play for Android Maps: "This new offline thingy is BS! Never works well, put asides, maps works only with a data connection, and constantly running in the background."