News for hackers. Stuff that matters.
Re:How Google designed its wildfire feature for Maps by lucasisola on Monday November 22, 2021 @10:57AM (#29307774)
Lol. I was coming to the comments section for this. There must be some challenge here that isn't immediately obvious because I feel that no one has solved this well.
Re:How Google designed its wildfire feature for Maps by rudian on Monday November 22, 2021 @11:18AM (#29308038)
I’m confident it’s two reasons:

- too many street names make for a noisy/busy/ugly map, and we all know maps must be beautiful and nothing else

- streets don’t pay for ads, businesses do, so between the two they prefer showing the latter.

Technically now you can tap anywhere on the map once to place a pin and get more info; In practice tapping in Google Maps has become horrendous, it never does what you expect. One such example is tapping on a business near a “walkable area”: you can’t. The area will always focus instead, even if painted behind the business.

Re:How Google designed its wildfire feature for Maps by squeaky-clean on Monday November 22, 2021 @11:29AM (#29308199)
Apple Maps does this really well (at least for NYC). It's the only reason I keep it installed, to look at street names while using Google Maps
Re:How Google designed its wildfire feature for Maps by bsedlm on Monday November 22, 2021 @12:15PM (#29308834)
> There must be some challenge here that isn't immediately obvious

the challenge is profit maximization, this to emphasize it is not a technical challenge (earlier versions of maps were good at this)