future-mvt VS Leaflet

> PMTiles aside, this is still Mapbox’s world.

Isn't this is a bit like saying we're still in Google's world because most maps still use Web Mercator? :)

Good tech builds on what came before. Mapbox did a lot of ground-breaking work in building tooling around OSM, but so have many others. The fact that they named it Mapbox Vector Tiles is be genius in hindsight, because even though we may use tons of tooling they didn't create to build and render them, their name is still there.

> The next challenge is to evolve the tech stack to something beyond what Mapbox worked up five/ten years ago.

Agreed, and I think we've seen a lot of iterative work in the open since then. The next challenge is likely building a OSS stack to do proper 3D: open data (including OSM) to pixels, and that work is already beginning across a lot of organizations: https://github.com/nyurik/future-mvt/discussions, Overture Maps, MapLibre, etc.

9. Leaflet

Leaflet is the most famous open-source map library, with lots of plugins. 2 of them are used to animate a marker on the map:

Leaflet stands out as one of the top open source JavaScript libraries for crafting interactive maps. Optimized for both mobile and web devices, it is relatively small (around 42KB) and offers a ton of features, plugins, and a straightforward API. It works across all browsers and platforms.

Finding maplibre 'better' was more valid at the time than today, and is also subjective. The creators and maintainers of both libraries have done some great work (and are still doing so).

Back in January 2022, the stable version of leaflet, v1.7.1, was from September 2020, and was affected by some small bugs degrading the user experience. Although the release of following version seemed close, there was no clear schedule for it, and I had concerns about how maintained the library would remain.

As of today, the bug from 2015 where there is some white space between map tiles on fractional zoom levels [0] is still open.

Also, leaflet was a pain to integrate in Svelte Kit framework, because it depended on `window` and-or `document`, not available at server side.

Maplibre, on the other hands, with a feature set roughly equivalent to Leaflet, benefited from much more frequent releases, and seemed more stable across browsers and devices. It was also easier to make it work in Svelte kit.

[0]: https://github.com/Leaflet/Leaflet/issues/3575

For a personal project, I had to use Leaflet with Svelte, and I faced some problems during development.

Do anyone have any workaround on how to get leaflet js to work inside notion, either as an embed or as code, or widget? https://leafletjs.com/

None of those things are what most in the GIS space would consider "complex", so you could go with any of the options you selected. For lightweight maps, I like Leaflet

https://leafletjs.com

I have a special place in my heart for Leaflet and it’s documentation: https://leafletjs.com

Its suppose to be free: like with map data providers there's Leaflet, OpenStreet Maps and many more which are all for free.