This was brought to my attention and was quite an amusing little bug. Try Google Maps Directions from "19020" to "1579 US-1 (S), North Brunswick, NJ. 08902". U will be in for a nice sUrprise.
a. Google Maps Directions Search Result (Incorrect)
b. Windows Live Virtual Earth Map Direction Search Result (Correct)
In all fairness, hiccups like these exist in other map services as well. This one was just particularly amusing and too hard to pass up.
Anyhow, onto more serious issues...
Google Mashup Consumers Get TeleAtlas instead of NavTeq Provider
While the following topic does not directly affect end users of both Maps sites, it does have a significant impact on mashup developers. (NOTE: one end user feature I will point out is the fact that Virtual Earth automatically readjusts to highlight your map route or center your location when you resize your browser window. Nice attention to detail)
You will notice that while Google Maps has Navteq as their provider for maps.google.com, mashups built with Google Maps API have TeleAtlas as their provider.
Meanwhile, Live Virtual Earth has Navteq as the provider for both its site and for mashup developers.
One of the most notable turnovers in the consumption of mashup services has been that of Redfin from Google Maps to Virtual Earth. It remains to be seen whether this tiered data provider approach will cause others to switch away from Google Maps API. While these may be cost driven strategies, ever since Blake Ross spoke out on "Don't Be Evil", it is difficult not to be sensitive to these user experiences or to any web security issues out of Google (today's being: Google's anti-phishing plugin leaked passwords). (reference: also see blog entry on security in software as a service.)