FYI: I just tried to define a custom marker in v3.

It took me two hours to define the marker's image and its shadow. The
needed code seems to be more extensive than in v2.

The code generally seems to be longer and more complex than in v2. I
think this necessity comes from the intention to keep the API code as
small as possible, so that the users have to write their special
features themselves.

This intention seems to be based on the opinion that the maps will
generally load and perform faster with lesser API code.

But this opinion is not generally true.

Lesser API code will not automatically lead to faster performance and
faster loading of the map in many cases. Exactly the contrary will
happen most of the time, namely the client's script code will
automatically be increased.

And these client scripts are in many many cases very inefficient. So
this will lead - more often than expected - to slower performance of
the map.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Maps API" 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?hl=en.

Reply via email to