The map itself may not be a way to solve anything, but the data it's collecting could be. Like you say, you prefer knowing proximity to subway stations - not just seeing a map. But the need to figure out that proximity is what makes collecting locational data (in a fun and user-friendly way, like OP's map) so important.
Regarding my apparent trolling, I think HN may have missed my point. Using the Google Maps API implies agreement to their ToS, which restricts one from using non-Google basemaps, and limits usage of the map in certain ways. While many people ignore, or are never affected, by usage limits, this still obligates developers to Google's quotas and pricing tiers (updated significantly in late 2013). There are other, similarly-implemented mapping APIs with more options, where you aren't locked-in to a particular vendor's load quotas. Tying OP's project to this particular API is a bit like saying "Support Local Businesses! ...click here for our Cafe Press site."
My point, which apparently made me a troll, is that by using the Google Maps API they will be directly contributing to the economy they're trying to change. It seems counterintuitive.
If you want to map your fight of The Man, why not use Mapbox, LeafletJS, etc. Something that doesn't lock you to a basemap provider and then charge for the privilege.
There are frequently better tools at hand, or at least different tools, or tools that offer a choice of values represented.
Since this "Quiet Revolution" (whatever it is) claims to oppose "corporate titans" (their words), and wants to talk about an economy more "in line with (their) values", I found their choice of tools interesting. That's all.
The map itself may not be a way to solve anything, but the data it's collecting could be. Like you say, you prefer knowing proximity to subway stations - not just seeing a map. But the need to figure out that proximity is what makes collecting locational data (in a fun and user-friendly way, like OP's map) so important.
Regarding my apparent trolling, I think HN may have missed my point. Using the Google Maps API implies agreement to their ToS, which restricts one from using non-Google basemaps, and limits usage of the map in certain ways. While many people ignore, or are never affected, by usage limits, this still obligates developers to Google's quotas and pricing tiers (updated significantly in late 2013). There are other, similarly-implemented mapping APIs with more options, where you aren't locked-in to a particular vendor's load quotas. Tying OP's project to this particular API is a bit like saying "Support Local Businesses! ...click here for our Cafe Press site."