My beef with GMaps is its performance. The UI is for the most part fine (though there some awful blunders that were later fixed). Loading GMaps takes forever n

My beef with GMaps is its performance. The UI is for the most part fine (though there some awful blunders that were later fixed). Loading GMaps takes forever now and brings my entire browser to a freezing stop (Chrome OSX) until it's done doing whatever it's doing. This is a modern desktop (i7, 16GB RAM, discrete graphics). Even after it's done "loading" if you try to interact with the map right away it does so at a crawl - inputs take multiple seconds to register and panning/zooming runs at about 2 frames a second. It takes about 10-15 seconds after load for the site to be fully functional and performant. That's insane. Ditto the Satellite view. Yeah, having 3D buildings is pretty cool and all, but the performance is atrocious on even fast, modern machines. If that's the tradeoff I'll take the 2D satellite imagery back please. Overall interacting with GMaps is itself a chore, and it almost entirely comes down to bad performance. This is especially frustrating on mobile if you put the performance of GMaps on iOS next to competitors like Apple Maps - the rendering performance is insanely low even on the most up to date hardware like an iPhone 6s. Beyond performance problems, one thing Google didn't fix until recently was that it was literally impossible to see information on an address/place and nearby transit at the same time. They changed Transit from a persistent overlay that can be toggled to a special view mode itself, which would disable itself the moment you clicked on any point of interest on the map. It makes me wonder if anyone on the Maps team lives in a major city.