Could you please explain (in brief) the mapping "ecosystem" as it were, and where Maplibre fits into the picture?
OpenStreetMap (OSM) is a community-driven, fully open and usable data library. It has usable data for almost the entire world for everything from cities, roads, houses, parks, country borders, and work. It's a database of everything you need to make map. They also have a website that renders that map, but it's not commercially usable.
Mapbox is one of the first companies to take OSM's dataset and commercialize it. Along the way they created a lot of the wildly used mapping libraries, including renders, data formats, and styling tools.
Mapbox Studio is one of Mapbox's proprietary tools for working with maps in their ecosystem.
Mapbox GL is a suite of renderers, originally entirely open source, developed by Mapbox with the community to render map data (from many different sources).
MapLibre GL is a community-driven fork of the Mapbox GL suite, after Mapbox closed the licenses to require payment if you use the latest versions.
OpenLayers and Leaflet are both alternative, open source renderers with various levels of capabilities. Interestingly, the creator of Leaflet now works for Mapbox (if my facts are correct and current).
The commercial players have mostly abandoned this approach, though, in favor of technologies that render on the client. They're more performant (tiles are smaller), and necessary if you want, say, to be able to rotate your map and still have all the labels be upright and not collide, or show/hide individual geographic features dynamically in response to user input, or apply perspective/tilt as you would for a heads-up display in a car, etc.
Mapbox GL was Mapbox building that (as already exists for Google Maps, Apple Maps, etc.). At a very high level, it and Leaflet serve a similar purpose, but are technically very different from one another.
(full disclosure: former Mapbox employee, still a shareholder)
Wall time CPU profiling is just not that useful anymore and yet it's the only thing most people ever think about for some reason.
I believe the reason most companies moved to vector had more to do with the other stuff gp mentioned: ability to rotate, dynamically show/hide features, etc.
These days Chrome and Firefox have the OffscreenCanvas API that would let you do all that rendering in a different thread, but last I looked MapBox GL didn't support it. Not sure if that's changed with libre.
Sorry for being so vague, that's just all I remember of the whole deal. I probably bookmarked the link, but I'll probably never find it again now.
Edit: it may have been MapZen that I was thinking about.
Leaflet: fairly simple open source mapping library. Canvas-based. The original Mapbox (called MapboxJS) is based on this.
Openlayers: open source mapping library that’s more capable (e.g many different protections) but also more complex. Can render to Canvas or SVG.
Openstreetmap: public and free source of mapping data. Mapbox uses this as a default data source.
MapboxGL: completely new implementation of a mapping library written in WebGL (should perform better). MapboxGL changed its license recently, prompting the creation of the libremap fork.
Mapbox GL/Maplibre - works with vector tiles which are similar in format to an SVG
I believe this plugin is a hybrid approach which allows Leaflet to load vector tiles on a plain 2D map with no map tilt or rotation
In Mapbox Studio, the features all seem to be semantically tagged (e.g. this is a road of type X, a POI of type Y) and it makes styling a cinch. I know OSM has its own set of tags for features. Are these compatible (not sure if Mapbox Studio is using OSM data underneath)? Is there an established standard for this type of thing?
(ps TY again for answering my other question so thoroughly)
All vector tile sources use tags in various ways, so Maputnik (and the resulting styles) do as well. There isn't a standard tagging schema (and all MVT sources tend to differ slightly), but OSM's tagging is often influential on the resulting schema.
Either way, the recommended way of connecting deck.gl with Mapbox is through React Map GL. Those docs describe how to use Maplibre GL here  and here .
I should note this is only the recommended way when you're using React
This works absolutely seamlessly.
I'm using Vue instead of the React integration and that's also working without any issues.
- A data source for vector tiles; there's a lot of options: https://stadiamaps.com (my company), https://maptiler.com/ & https://jawg.io (other core contributing companies), among others.
- A style that matches. I'm not aware of an open source style that closely mirrors OSM's style using MapLibre GL Styles (also forked from Mapbox). OSM Bright is pretty close: https://github.com/mapbox/osm-bright / https://github.com/openmaptiles/osm-bright-gl-style.
There is an issue about converting it to vector: https://github.com/gravitystorm/openstreetmap-carto/issues/3...
Doesn't seem like there's any current vector versions of that style, but you could make one yourself using Maputnik or similar; you'd probably want to start with OpenMapTiles and maybe even one of the pre-existing styles for OMT like OSM bright.
When adding clusters vs points to a map, filtering points is really simple, but I haven't found a simple way to filter clusters outside of filtering a data source and reapplying it to the clusters.
If there a better way of doing this?
The obvious downside of this is that the cluster positions aren't accurate because they're based on points that are supposed to be hidden, but it's fast and doesn't require recalculating.
Desktop support should be possible with some extra work with Native, but I'm not certain, for instance, if the QT bindings are fully working yet.
We are using MapTiler along with MapBox GL JS. It seems that MapLibre GL JS is our next logical upgrade step. For one it's great that you have a Leaflet plugin under your github org.
The latest mac version of Libreoffice is nearly unusably laggy even on brand new fast hardware with lots of ram, and it looks like garbage to boot.
Insulted? Abused? What are you talking about?
The SDK is just a library, used to render vector map tiles, usually in the MVT-format: https://docs.mapbox.com/vector-tiles/specification/
Most maps rendered with such an SDK are based on OpenStreetMap data.
Mapbox uses data from OSM among others when they create their tiles. https://docs.mapbox.com/help/getting-started/mapbox-data/#co...
Would you please provide a way for the user to deactivate that terrible idea ? Thanks.
Will the SDK also work on iOS and Mac then, i.e. has Metal support?
https://github.com/maplibre/maplibre-gl-native/tree/metal-su... is the branch and https://github.com/maplibre/maplibre-gl-native/issues?q=is%3... are associated issues.
There is active development on a Metal-supporting version.