Regarding that: What about any of those fancy frameworks with so-called "server-side rendering"? (I prefer the term "templating").
In particular: Do you think that the advantages of a SvelteJS port of Leaflet (e.g. ability to not use JS on the client) would be worth the problems (e.g. state transition animations, loss of canvas rendering)?
Engineer at Mapbox, creator of Leaflet, open source enthusiast, algorithms geek, speaker, singer-songwriter (Obiymy Doschu), father of twin girls, Ukrainian
I never thought about it, but it would be cool to explore. :) It's hard to imagine how a JS-less interactive map would look like though — like in pre-Google Maps era with a static image and buttons for panning that reload it?
I'd settle for something that is capable of templating all the HTML for the initial state of the map server-side, yet allow for JS-ful interaction afterwards. :-)
Regarding that: What about any of those fancy frameworks with so-called "server-side rendering"? (I prefer the term "templating").
In particular: Do you think that the advantages of a SvelteJS port of Leaflet (e.g. ability to not use JS on the client) would be worth the problems (e.g. state transition animations, loss of canvas rendering)?
I never thought about it, but it would be cool to explore. :) It's hard to imagine how a JS-less interactive map would look like though — like in pre-Google Maps era with a static image and buttons for panning that reload it?
I'd settle for something that is capable of templating all the HTML for the initial state of the map server-side, yet allow for JS-ful interaction afterwards. :-)
MultiMap FTW