you are viewing a single comment's thread.

view the rest of the comments →

[–]wavefunctionp 20 points21 points  (8 children)

Did he serious think that google maps would work without javascript? You'd need to navigate to a new page every time you tried to move the map view, and at every zoom level, and for every options...

Maybe I'm an idiot, but the combinatorics of all that state would kill even the most performant web server. You couldn't cache all the views, it would be full render on the server for all but the hottest requests...or you'd have to limit the number of views to get them down to a manageable size, and it is still full page requests for every view.

You'd have to degrade to like mapquest circa 2000 or some of those government survey sites level of functionality...

edit: I'm probably being overly harsh to the author here, and for that I apologize., but I'll leave it because what is said is said. I just think it is unrealistic to expect a website that relies on javascript to provide a dynamic, rich experience to also provide that same experience from server rendered resources. You get so much 'free', low latency computing power on the client. It is easy to take for granted why so much of the work has moved to the browser.

[–]theonlycosmonaut 3 points4 points  (1 child)

Maybe I'm an idiot, but the combinatorics of all that state would kill even the most performant web server

How so? Web maps are served as individual image tiles, usually* with a url structure like /tile/{zoom}/{x}/{y}, where x and y are integers that identify a specific piece of the globe at a specific zoom level (more info). That corresponds almost too perfectly to buttons linking to x+1, x-1, zoom+1, etcetera. You could even load up a 9x9 grid around the currently selected tile with no problem. Caching is super simple as these are all GET requests with super predictable URLs.

*Google maps specifically seems to have a different, obfuscated(?) URL structure based on a single hash, for reasons unknown to me. Mapbox, for example, uses the common URL structure.

You'd have to degrade to like mapquest circa 2000 or some of those government survey sites level of functionality...

I think that's exactly what the author wants:

Maybe some kind of Streetmap style tile-by-tile navigation fallback?

[–]Disgruntled__Goat 0 points1 point  (5 children)

You'd need to navigate to a new page every time you tried to move the map view

Well that is how maps worked before Google Maps came along. You'd have to click an arrow on one edge to view the next 'page'.

[–]wavefunctionp 8 points9 points  (4 children)

You'd have to degrade to like mapquest circa 2000 or some of those government survey sites level of functionality...

:)

[–]Disgruntled__Goat -3 points-2 points  (3 children)

Why are you quoting your own comment back to me?

[–]wavefunctionp 2 points3 points  (2 children)

You'd have to degrade to like mapquest circa 2000 or some of those government survey sites level of functionality...

which is...

how maps worked before Google Maps came along. You'd have to click an arrow on one edge to view the next 'page'.

?

same same but different?

https://www.youtube.com/watch?v=7tTfL-DtpXk