Why NUKEMAP isn’t on Google Maps anymore

When I created the NUKEMAP in 2012, the Google Maps API was amazing.1 It was the best thing in town for creating Javascript mapping mash-ups, cost literally nothing, had an active developer community that added new features on a regular basis, and actually seemed like it was interested in people using their product to develop cool, useful tools.

Today, pretty much all of that is now untrue. The API codebase has stagnated in terms of actually useful features being added (many neat features have been removed or quietly deprecated; the new features being added are generally incremental and lame), which is really quite remarkable given that the Google Maps stand-alone website (the one you visit when you go to Google Maps to look up a map or location) has had a lot of neat features added to it (like its 3-D mode) that have not been ported to the API code (which is why NUKEMAP3D is effectively dead — Google deprecated the Google Earth Plugin and has never replaced it, and no other code base has filled the gap).

Stories like this often confuse me. Google’s behaviour seems designed specifically to harm the people most enthusiastic and knowledgeable about their products, pushing them away to use competitors’ products or other alternatives. While that won’t harm Google’s bottom line in the short term – and, in fact, might even improve it – in the long term, it strengthens alternatives and teaches people to untangle themselves from Google’s web of products.

What’s in it for Google here? Is this just clueless bean counters lead by bottom line-obsessed executives? Or is there some grander plan behind pushing people away?


  1. 2019-12-13 8:16 pm
  2. 2019-12-13 8:31 pm
    • 2019-12-13 8:33 pm
  3. 2019-12-14 6:11 am
  4. 2019-12-14 8:21 am
    • 2019-12-14 7:17 pm
      • 2019-12-15 2:55 am
  5. 2019-12-16 9:10 am
  6. 2019-12-16 10:48 am
  7. 2019-12-16 12:05 pm
  8. 2019-12-16 1:14 pm
  9. 2019-12-16 4:22 pm
  10. 2019-12-18 3:22 pm