A couple of days ago Google unveiled their Beta version of a new Maps interface, which provides bike route recommendations across America. It's a vast undertaking, with a lot of nuances to factor in, but that didn't stop the Post from saddling up to nitpick Google to the max. (If we didn't know better, we'd think the Post has some sort of ax to grind with Google.) One day after it was launched, a reporter for the tabloid pedaled around and took Google to task for several shortcomings around NYC, such as:

In Brooklyn, Google steers cyclists into the path of anti-bike Hasidic Jews by designating Bedford Avenue between Division and Flushing avenues in Williamsburg as a legitimate bike route. The city sandblasted away that street's bike lane last year after protests.

Daaaamn, Google just got pwnd! Oh wait, that's actually a pretty weak complaint, because the bike lane only partially disappears for about a dozen blocks, and then picks up again. (It's actually still basically there, because the DOT left one of the white lines from the old bike lane.) Also, are Hasidic Jews standing by with pitchforks to spear bike riders in South Williamsburg? If so, we don't see them on Google Street View.

The article also calls Google out for misidentifying some footpaths as bike paths in Central Park, and sending cyclists to Jersey via the GW on the north side, although the "official" bike path is actually on the south side. Then there's this, which, while valid, sounds sounds so persnickety it would fit right in as a Gothamist comment: "Google Maps sends cyclists on a hazardous 30-block stretch of Frederick Douglass Boulevard... A safer pick would have been up St. Nicholas Avenue." Ugh, can't Google do anything right? It's not as if New York is a massive city with hundreds of miles of bike lanes constantly in flux. Like the Post, we'll wait for Bing to come out with a bike mapping feature, thank you very much.