Earlier quoted context omitted.
> so I've noticed that I do want a map that works like a map - something I can explore and annotate. I don't doubt that there are use cases for a map that works this way. Even if Google Maps covers 80-90% of the use-cases for mapping, mapping is an absolutely massive domain. 10-20% of use-cases still represents a huge volume. But it doesn't have to be Google Maps. It actually seems worse to be for one "maps" app try…
pretty much all games in the early 80's had [so called] pixel perfect scrolling. Each frame showed exactly what was required. Today it is entirely acceptable for a map to be a jerky stuttering pile of crap. The same goes for the infinite scroll implementations. Its preposterous to start loading things after they are needed. There is a good analogy with making things in the physical world. The professional doesn't sta…
There's a huge gulf between the use cases you're comparing here, and I don't believe for one second that loading the Google Maps dataset into Commander Keene's engine would make for a better experience.
(Also, not to be overly pedantic, but "The professional doesn't start a job before he has everything he needs to do it" pretty much classifies all building construction as unprofessional. The professional doesn't magically have everything on-hand, especially bulky or expensive resources; they have a plan for acquiring them at reasonable rates of input and mitigation strategies if that plan can't be followed)