Slashdot Mirror
Do You Recommend Google Maps API or Microsoft Live Maps?
KSobby writes "The organization that I work for is going to be redoing our website in .Net/AJAX. On the site, our members will have profile pages listing where their organizations are located (our members are scattered throughout the world) as well as other pertinent information for the general public. It is a non-profit organization, so funds are tight. My question to you: If we include maps, which API do we go with: Google or Microsoft? We're in a Microsoft environment (we're non-profit and Microsoft basically gives us everything for free) but the ubiquity of Google may be enough to sway us. Has anyone used either extensively? Used them in conjunction with .Net?"
afwafgearfgeargvf
Mr. Pibb + Red Vines = CRAZY DELICIOUS
i don't have anything to add to this thread.
USCARRp70a
With Google's new "change the route" - it's cool. Yahoo's maps (old) is better, the new one has issues with moving the maps around (It frequently wants to go back!).... Mapquest sucks (Honest Question: why does anyone use it? - have you seen any of the other map tools?) Yahoo maps also lets me type in notes when I print out the map to actually _drive_ somewhere.
>>I say go with Google. If their map system suddenly changes they'll at least be smart enough to include legacy support or do something remotely responsible and there's no way that their entire map system would just disappear.
Someone is certainly not a Microsoft fanboy, eh ?
Its obvious you haven't spent much time with Microsoft software. There's absulutely no other commercial vendor that goes to the extent Microsoft goes to in order to maintain backward compatibility. If you have ever wondered why code is Microsoft code is bloated the answer is backward compatibility. If you have wondered why a supported standard is not the latest and shiniest new standard the answer is again backward compatibility. You should go out and read sometime about Microsoft's appcompat (application compatibility) labs, it will help widen your views. This may surprise you but there have been documented instances where a vendor of an application has incorrectly used an OS API, resulting in the application breaking when a new Windows version or Service Pack is released. Microsoft is known to implement application specific workarounds to allow the incorrectly written application to contiue working in the interest of appcompat.
>>As for Microsoft, they change their names and systems more often than I change my pants and if suddenly all of that new Microsoft Live crap disappeared, nobody would be surprised at all.
Microsoft has documented and published support policies for each version of their software so at any time you can know what level of support you are entitled to for what you purchase. The MS Maps service may have gone through name changes, but they've been around for over 5 years now. With the announced 1.3B they are shovelling into the Live services for FY2008, its more likely your pants will be discarded by you before the service dies.
Right. Evidence. That's what I was missing. Thanks, that is most definitely my point. Microsoft just extended the end of life of XP by another six months. I too dislike supporting old products six years after it's been sold, but hey, that's what the clients want.
Bowing to what clients want is not humiliating, it's a point of pride. Not everyone can do it. I'll be transitioning my primary development machine to Vista -- the last in the office, and by far my favourite PC -- in January from windows 98 -- it's been my favourite PC for almost a decade now. I've enjoyed my various Vista experiences over the Summer, and my business is now moving into one or two Vista-based service offerings.
But it takes a good business to recognize the fun of a new windows version. Valid objections revolve around lack of drivers, lack of software, and lack of funds. But one simply must recognize that the first two are temporary, and the last is a business decision in both directions. We like new versions of windows, it's a big help in trying to convince clients to purchase hardware, so that they can purchase software, so that they can purchase me.
Hi
Of all the comments I have seen on Slashdot, I have never been so Horrified as yours. I am glad you have stopped trolling. You sound Inteligent and coherent. The fact that you have just had so many of your fundamental legal rights breached in one go is astonishing. The fact that you have just rolled over when it happened is even more so. Don't get me wrong trolling is annoying and wasteful, but it is just banter, and not illegal. Illegal would be either pretending to be an FBI agent (which is what I think has happened here) or starting an FBI investigation on someone who annoys you. The intimidation of using the FBI badge to settle a personal squabble is not just a firing offence, it is a jail offence. Slashdot is just a website. It is not stalking when you troll. I assume you werent threatening him/her, or persueing him her through any other means. If this really was an FBI agent, then you should (no REALLY YOU SHOULD) report these actions. If this guy is using the fact that he works for the FBI as a big brother to intimidate people from a website (more ACCURATELEY SLASHDOT WHERE IT IS ALL PART OF THE SCENERY) imagine what he does if someone owes him money!!!.
Move along... there is no sig here.