Wow - you guys are focused on new and cool stuff (your opinion) even if it gets in the way of using maps for something primitive, like a map.
Remember, just because you can doesn't mean you should. On Saturday, August 27, 2011 at 6:32:48 AM UTC-4, Thor Mitchell (Google Employee) wrote: > > > > On Friday, 26 August 2011 14:54:36 UTC+1, Andrew Leach wrote: >> >> On Aug 26, 9:54 am, Pil <wol...@gmail.com> wrote: >> > >> > I think that's the point: It's always a good idea to release new >> > features and to continue development. >> > >> > But as soon as a new feature becomes the default one, people have to >> > fiddle around with their existing map - either instantly or six months >> > later. >> >> I concur. The "principle of least astonishment" applies to developers >> as well. New features should default to the state they had before >> their introduction -- so for example, if business icons are >> introduced, they should default to "off"; but if (say) existing labels >> become optional they should default to "on". > > > That's a sure fire way to end up with a really ugly programmatic > interface. It means that any new developer who starts using the API and > wants their map to behave as closely to Google Maps as the API supports > (which is normally the case) has to explicitly opt-in to every new feature > that has been added to the API since it was first launched. > > There is also the issue of feature discoverability. We learned the hard > way in v2 that expecting developers to discover features and opt-in to them > is unrealistic. You end up with 95%+ maps doing nothing more than the > absolute minimum (a few default markers). We want new Maps API apps to be > as featureful as possible, and existing Maps API apps to benefit from the > work we are doing (or we might as well just stop doing it). To do this, we > ensure that v=3 delivers the most complete experience we can offer, but we > recommend that you opt-out of that experience in production so you don't > get caught out. > > Use v=3 in your development environment though, and you will see the > improvements as they happen, and can decide on a case by case basis how to > respond before they hit your production environment. > > Many thanks, > > Thor. > > >> **Then** it's up to the >> developers how they make their map match Google Maps and provide the >> *user* with least astonishment (the map they use changing, or that map >> not matching Google Maps). Google are becoming almost as paternalistic >> as Microsoft, and that's a comment which hopefully Larry Page wouldn't >> have dreamt of ten years ago. >> >> And pharmacies are definitely businesses, not medical establishments. > > -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-maps-js-api-v3+unsubscr...@googlegroups.com. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. Visit this group at https://groups.google.com/group/google-maps-js-api-v3. For more options, visit https://groups.google.com/d/optout.
