Engineer at Mapbox, creator of Leaflet, open source enthusiast, algorithms geek, speaker, singer-songwriter (Obiymy Doschu), father of twin girls, Ukrainian
I don't see Leaflet getting many new features — its whole point is to remain small, simple and lightweight, and given it's maturity, there's not much left to add. I'd actually be happy if we manage to remove some features. :) So the main focus would be on bugfixes, performance, refactoring it to make it even simpler, better docs, more examples, and more extensibility points for plugin authors. However, I won't be against taking Leaflet to a new direction if the community and its other maintainers decide that it's the right choice.
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. :-)
Beyond bugfixes and dropping support for eg non-ES6 browsers, what do you see as future developments for Leaflet?
I don't see Leaflet getting many new features — its whole point is to remain small, simple and lightweight, and given it's maturity, there's not much left to add. I'd actually be happy if we manage to remove some features. :) So the main focus would be on bugfixes, performance, refactoring it to make it even simpler, better docs, more examples, and more extensibility points for plugin authors. However, I won't be against taking Leaflet to a new direction if the community and its other maintainers decide that it's the right choice.
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