Atlas tool question: Desktop vs. Web
This may be obvious to tech folks but can someone explain why the Atlas tool renders so much faster in my web browser than in the desktop app if they're both using the same internet connection and graphics processor?
If the desktop app rendered the Atlas tool as fast as the web app I'd be much happier with it. Why would there be such a disconnect between the two?
Comments
-
Why would there be such a disconnect between the two?
I don't know if you are going to get a definitive answer, but I assume that the issue surrounds additional levels of software. The desktop app isn't a web browser, although it has parts of Chromium in its code. When flying from coast to coast, a non-stop flight is faster than one with a layover.
0 -
When flying from coast to coast, a non-stop flight is faster than one with a layover.
That actually makes sense. I don't use the Atlas tool that much (partly because it's slow, partly because I can't always get the precise places I'm searching for to appear on the map the way I want. I typed in Jerusalem and literally couldn't get it to show up on the map, but I could see Emmaus and Bethany). I prefer to use the Biblical Places maps and that will likely still be my go-to, however I may start also using the Atlas tool in the web browser from here on out.
0 -
Adding to the guesswork, I'd suspect it's the servers. Just from watching the mobile tools vs web. I'd bet there's a grand central station built back in 2008, and then patched, expanded, re-routed, etc. The web is over at Newark International and no security line for graphics. Text however goes thru security ... slow. Oddly. Maybe uses the grand central shuttle.
But you're right ... I was surprised at the web atlas. My last desktop experience was very slow. Of course, 4 years back.
0
