I understand you are angry about them depreciating the flash api, but 2 years is a long time in technology. I am sure you can find some angry cobalt developers. Also I don't know where this illusion about microsoft comes from, they have dumped tons of projects, want to talk about a sinking ship, their online division is currently bleeding a billion dollars a quarter. In reference to their apis, the google Javascript API has always been under development and predates the flash API significantly.
Yes Pamela Fox was exceptional, and she was very unique, but when I talked with her at Google IO even she said, no one uses the flash API when I asked why the flash API wasn't getting styled maps at the same time. This is technology dude, if you think microsoft is any different you're really delusional. You might not be aware of this but Google's flash API was actually acquired from the same guys which gave bing it's first flash support (umapper). Two years is more then enough time for a depreciation period, and who knows there might be a good reason for them to pull it out of depreciation. Whenever you use third party anything there is always the chance that this could happen. I will admit, that I do think the depreciation was brought on about 1-2 years too early, ces't la vie. All my future projects are using the Google Javascript API, I am not really concerned about depreciation of that API, and so far it looks like their quotas will actually be cheaper then bing's. -- 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/-/d9HKpn0tA14J. To post to this group, send email to google-maps-api-for-flash@googlegroups.com. To unsubscribe from this group, send email to google-maps-api-for-flash+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-api-for-flash?hl=en.
