I didn't lose any clients. I'm just explaining how the method that they used to depreciate the map was horrific and I am sure it will affect many relationships with clients. You can't blame a client that paid $10,000 to get an application built that only works for a few years before it needs to be redone. After 1 year they should be working on version 2 not starting on a new version 1 again. Or all the people that built Android apps with Google Maps using the Flash API because Google said they were expanding support. Now devolpers have a real expensive text file with AS3 code sitting on their computer.
Yes Bing can kill the map at anytime but they are a company that strives on developers. They aren't going to kill something unless it is absolutely useless. IE6 lasted forever and XP is still supported for security updates. I wasn't referring to ASP.NET the framework I was talking about the website asp.net that provides help for ASP.NET and other things like Jquery. But that is my point, Microsoft's business is to create tools for developers. They sell them to both the server company and the programmer. Google wants you to make enough stuff that they can use so the can make money off of it. Microsoft is way more likely to kill something slowly and fairly then Google is. Your point about Bing the search engine still doesn't show Microsoft is a sinking ship. They are spending millions to attract new advertisers and build a search engine. They are expanding their business and it costs money. But again that is my point they are a company that favors developers not a marketing company that uses developers. On Jan 8, 2012 9:10 AM, "Jonathan Wagner" <[email protected]> wrote: > I am in a similar boat with some clients that utilizing the flash API, I > was fortunate enough to tell them they would need to switch to javascript > in the future. While it would take some work, I could move to another flash > based API within the application. If the client is blaming you for > something Google did, I am pretty sure you don't want that client anyways. > > Also comparing a back-end server language is not the same as a connected > online API. If you read through bing's map TOS it reads almost identically > to the Google TOS. They can cancel services, they are not liable etc.. > etc.. Also in scale of course asp.net would have higher quality support > then the flash maps api, in the same way the google javascript API has > better support, it's about resources. I am pretty sure if you're using a > microsoft product that very few people use, you're not going to get the > same quality of support as you would with asp.net. > > I haven't done any form of bench marking yet, but V3 seems fast. Also here > is a link to the article > http://money.cnn.com/2011/09/20/technology/microsoft_bing/index.htm > > It sucks you lost a client, however I would be hesitant of judging Google > based just on the flash maps API depreciation. It's a big company, not > everyone at it decided they wanted to depreciate the flash maps API. > > -- > You received this message because you are subscribed to the Google Groups > "Google Maps API For Flash" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-maps-api-for-flash/-/o6cTyU-pQR8J. > To post to this group, send email to > [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-maps-api-for-flash?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Maps API For Flash" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-api-for-flash?hl=en.
